Veritas InfoScale™ for Kubernetes Environments 8.0.300 - 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
- 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
- Migrating applications to 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.300.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 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 assign a clusterrole to infoscale-admin. You must be logged in as a super user.
- kubectl config use-context kubernetes-admin@kubernetes
You have switched the context to
kubernetes-admin@kubernetes
. - kubectl apply -f /YAML/Kubernetes/infoscale-admin-role.yaml
Here,
infoscale-admin-role.yaml
is downloaded as a part ofYAML_8.0.300.tar.gz
. - kubectl create clusterrolebinding infoscale-admin-clusterrolebinding --clusterrole=infoscale-admin-role --user=infoscale-admin
This step binds the cluster role
infoscale-admin-role.yaml
to a new user -infoscale-admin
. - openssl genrsa -out infoscale-admin.key 2048
You have generated a key for
infoscale-admin
by using 2048 bits.openssl req -new -key infoscale-admin.key -out infoscale-admin.csr -subj "/CN=infoscale-admin"
You have created a certificate signing request for
infoscale-admin
.openssl x509 -req -in infoscale-admin.csr -CA /etc/kubernetes/pki/ca.crt -CAkey /etc/kubernetes/pki/ca.key -CAcreateserial -out infoscale-admin.crt -days <Number of days>
The certificate is signed by Kubernetes, a crt file is created, and is valid for the number of days you specified in the command.
- mkdir /certs && mv infoscale-admin.crt infoscale-admin.key /certs
infoscale-admin.crt
andinfoscale-admin.key
moved to/certs
folder for thelico.yaml
to reference. - cd /certs
kubectl config set-credentials infoscale-admin --client-certificate=/certs/infoscale-admin.crt --client-key=/certs/infoscale-admin.key
kubectl config set-context infoscale-admin.context --cluster=kubernetes --user=infoscale-admin
kubectl config use-context infoscale-admin.context
Credentials are set for
infoscale-admin
and its context created. - kubectl config current-context infoscale-admin.context
Ensures that the current context is
infoscale-admin.context
.
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.300-<rhel8/ol8> with image: <IP address of custom registry>/infoscale-sds-operator:8.0.300-<rhel8/ol8>.
Edit
/YAML/Kubernetes/lico.yaml
as under -Replace image: 192.168.1.21/veritas/infoscale-licensing-operator:8.0.300-ol8 with image: <IP address of custom registry>/infoscale-licensing-operator:8.0.300-<rhel8/ol8>.
Edit
/YAML/DR/Kubernetes/dro_deployment.yaml
as under -Replace image: 192.168.1.21/veritas/infoscale-dr-manager:8.0.300-rhel8 with image: <IP address of custom registry>/veritas/infoscale-dr-manager:8.0.300-<rhel8/ol8>.
Optionally, if you want to change the default kubelet path, edit
/YAML/Kubernetes/iso.yaml
as under.env: - name: KUBELET_PATH value: <enter the new path>
The default path is
/var/lib/kubelet
.Note:
Do not change the kubelet path after clusters are configured.
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