Veritas InfoScale™ for Kubernetes Environments 8.0.200 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Prerequisites
- Tagging the InfoScale images on Kubernetes
- Installing InfoScale on Kubernetes
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Administering InfoScale on Containers
- Upgrading InfoScale
- Troubleshooting
Installing InfoScale on Kubernetes
All information about the worker nodes must be added to the cr.yaml
file. All worker nodes become part of InfoScale cluster after cr.yaml
is applied. After you download, unzip, and untar YAML_8.0.200.tar.gz
, all files required for installation are available.
Note:
You must download images required for installation from the Veritas Download Center and push those to the Custom registry.
Configure a new user - infoscale-admin, associated with a Role-based Access Control ( RBAC) clusterrole defined ininfoscale-admin-role.yaml
, to deploy InfoScale and its dependent components. infoscale-admin as a user when configured has clusterwide access to only those resources needed to deploy InfoScale and its dependent components such as SRO/NFD/Cert Manager in the desired namespaces.
To provide a secure and isolated environment for InfoScale deployment and associated resources, the namespace associated with these resources must be protected from access of all other users (except super user of the cluster), with appropriate RBAC implemented.
Run the following commands on the master node to create a new user - infoscale-admin and a new project and assign role or clusterrole to infoscale-admin. You must be logged in as a super user.
- kubectl create ns <New Project name>
namespace/<New Project name> created
indicates that a new project is created.
- kubectl create rolebinding infoscale-admin --namespace=<New Project name> --clusterrole=admin --user=infoscale-admin
Following output indicates that administrator privileges are assigned to infoscale-admin within the new project.
rolebinding.rbac.authorization.k8s.io/infoscale-admin created
- kubectl apply -f /YAML/Kubernetes/infoscale-admin-role.yaml
Following output indicates that a clusterrolebinding is created.
clusterrole.rbac.authorization.k8s.io/infoscale-admin-role created
- kubectl create clusterrolebinding infoscale-admin-role --clusterrole=infoscale-admin-role --user=infoscale-admin
Following output indicates that a clusterrole created is associated with infoscale-admin by using a specified ClusterRoleBinding.
clusterrolebinding.rbac.authorization.k8s.io/infoscale-admin-role created
You must perform all installation-related activities by logging in as infoscale-admin. A cluster super-user can also install InfoScale.
Edit
/YAML/Kubernetes/iso.yaml
as under -Replace image: 192.168.1.21/veritas/infoscale-sds-operator:8.0.200-<sles15/rhel8/ol8> with image: <IP address of custom registry>/infoscale-sds-operator:8.0.200-<sles15/rhel8/ol8>.
Run the following command on the master node to install Veritas InfoScale.
kubectl create -f /YAML/Kubernetes/iso.yaml
Run the following command on the master node to verify whether the installation is successful
kubectl get pods -n infoscale-vtas|grep infoscale-sds-operator
An output similar to the following indicates a successful installation. READY 1/1 indicates that Storage cluster resources can be created.
NAME READY STATUS RESTARTS AGE infoscale-sds-operator-6dc9bc8856-lh72f 1/1 Running 0 2d18h