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
Prerequisities
The cluster status must be 'Running'.
On an OpenShift cluster, run oc get infoscalecluster.
On a Kubernetes cluster, run kubectl get infoscalecluster.
Review output as under
NAME NAMESPACE VERSION STATE AGE infoscalecluster-dev infoscale-vtas <current version> Running 24h
The cluster state must be 'Healthy'.
On an OpenShift cluster, run oc get infoscaleclusters.infoscale.veritas.com infoscalecluster-dev -ojsonpath='{.status.clusterState}{"\n"}' Healthy.
On a Kubernetes cluster, run kubectl get infoscaleclusters.infoscale.veritas.com infoscalecluster-dev -ojsonpath='{.status.clusterState}{"\n"}' Healthy.
System returns as under
Healthy
Guidelines to follow if DR is configured
DR controller must be upgraded after InfoScale upgrade is complete.
Ensure that any migration or takeover operation is not in progress during upgrade.
Veritas recommends upgrading the secondary cluster first followed by the primary cluster.