Veritas InfoScale™ for Kubernetes Environments 8.0.100 - 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
- Tech Preview: Configuring KMS-based Encryption on an OpenShift cluster
- Tech Preview: 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
- Troubleshooting
Additional steps for Azure RedHat OpenShift(ARO) environment
For a Azure RedHat OpenShift(ARO) cluster, in addition to plumbing the Virtual IP address inside pods; you must create a secondary IP address configuration. Complete the following steps on the primary and secondary clusters.
- Run the following command on the bastion node.
oc describe infoscalecluster -n infoscale-vtas
Note the name of the master node similar to the following output.
Node Name: sdsqacl03-wgnwr-worker-eastus21-dj76n Role: Joined,Master
Use this node name in the next command.
- Run the following commands on any node which has access to Azure CLI and login by using the Service Principal which was used to create the ARO cluster.
az login --service-principal -u <service principal> -p --tenant <tenant id> to login.
After you successfully login to Azure, run the following command to create a secondary IP address configuration.
az network nic ip-config create --resource-group <resource group> --nic-name <NIC name of the "Infoscale master node", as seen from azure portal> --private-ip-address <datarep IP address which was given for local cluster in datarep yaml> --name extraIP