Veritas InfoScale™ for Kubernetes Environments 8.0.220 - 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
Tagging the InfoScale images on Kubernetes
Complete the following steps to upload and tag InfoScale images in the private registry/repository and prepare the cluster for installing InfoScale.
Prerequisites
You must have a docker registry or you must set up a new docker registry.
If the registry is insecure, your Kubernetes nodes must be configured to access the registry by using
http
method.
Complete the following steps
Download
Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
andsetup_vtas_registry.sh
from the Veritas Download Center to a node where the private repository is configured.Note:
setup_vtas_registry.sh
is available intools_8.0.220.tar.gz
.Run the following command on this node
setup_vtas_registry.sh -c <IP address of custom registry>:<port number>/vtas_test -t Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
If you want to install InfoScale on an AKS cluster, run the following command.
./setup_vtas_registry.sh -c <Name of the Azure Cluster Registry>.azurecr.io -t Veritas_InfoScale_8.0.220_Containers_Ubuntu_Linux.tar.gz
After this command is successfully run, you have the ISO image as <IP address of custom registry>:<port number>/vtas_test/infoscale-sds-operator-8.0.220-<sles15/rhel8/ol8>
and CR custom registry as <IP address of custom registry>:<port number>/vtas_test
.
Alternatively, you can download Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
and individually load, tag, and push each image file. See the following steps.
Download
Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
and run the following command to extract the tar file.tar -xvf Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
After you unzip and untar
Veritas_InfoScale_8.0.220_Containers_<OS>_Linux.tar.gz
, you get the following image filesinfoscale-sds-8.0.220-<os-version>.img
infoscale-sds-operator-8.0.220-<os-version>.img
infoscale-sds-operator-bundle-8.0.220-<os-version>.img
infoscale-sds-operator-catalog-8.0.220-<os-version>.img
infoscale-licensing-operator-8.0.220-<os-version-major>.img
infoscale-licensing-operator-bundle-8.0.220-<os-version-major>.img
infoscale-licensing-operator-catalog-8.0.220-<os-version-major>.img
infoscale-fencing-2.0.200-<os-version-major>.img
infoscale-csi-2.0.200--<os-version-major>.img
infoscale-dr-manager-8.0.220-<os-version-major>.img
infoscale-dr-manager-bundle-8.0.220-<os-version-major>.img
infoscale-dr-manager-catalog-8.0.220-<os-version-major>.img
You must load, tag, and push each image file into the custom registry.
Note:
The following commands are applicable to docker as the runtime environment. These commands change as per your container runtime environment. Refer to the documentation for the equivalent commands.
For
infoscale-sds-operator-8.0.220-<os-version>.img
, run the following commands-docker load -i infoscale-sds-operator-8.0.220-<os-version>.img
docker tag localhost/veritas/infoscale-sds-operator-8.0.220-<os-version> <IP address of custom registry>:<port number>/infoscale-sds-operator-8.0.220-<os-version>
docker push <IP address of custom registry>:<port number>/ infoscale-sds-operator-8.0.220-<os-version>
For
infoscale-licensing-operator-8.0.220-<os-version-major>.img
, run the following commands-docker load -i infoscale-licensing-operator-8.0.220-<os-version-major>.img
docker tag localhost/infoscale-licensing:8.0.220-<os-version-major> <IP address of custom registry>:<port number>/ infoscale-licensing-operator-8.0.220-<os-version-major>
docker push <IP address of custom registry>:<port number>/ infoscale-licensing-operator-8.0.220-<os-version-major>
For
infoscale-sds-8.0.220-<os-version>.img
, run the following commandsNote:
You must be ready with the kernel version of the Operating system on each worker node. You can run uname -r to know the kernel version. If worker nodes have different kernel versions, you must run the following commands separately for worker nodes with identical kernel versions.
docker load -i infoscale-sds-8.0.220-<os-version>.img
docker tag localhost/infoscale:8.0.220-<os-version>-<kernel-version> <IP address of custom registry>:<port number>/infoscale:8.0.220-<os-version>-<kernel-version>
docker push <IP address of custom registry>:<port number>/infoscale:8.0.220-<os-version>-<kernel-version>
For
infoscale-fencing-2.0.200-<os-version-major>.img
, run the following commands -docker load -i infoscale-fencing-2.0.200-<os-version-major>.img
docker tag localhost/veritas/infoscale-fencing-2.0.200-<os-version-major> <IP address of custom registry>:<port number>/infoscale-fencing:2.0.200-<os-version-major>
docker push <IP address of custom registry>:<port number>/ infoscale-fencing-2.0.200-<os-version-major>
For
infoscale-csi-2.0.200-<os-version-major>.img
, run the following commands -docker load -i infoscale-csi-2.0.200-<os-version-major>.img
docker tag localhost/veritas/infoscale-csi-2.0.200-<os-version-major> <IP address of custom registry>:<port number>/infoscale-csi-2.0.200-<os-version-major>
docker push localhost/veritas/infoscale-csi-2.0.200-<os-version-major> <IP address of custom registry>:<port number>/infoscale-csi-2.0.200-<os-version-major>