Veritas InfoScale™ for Kubernetes Environments 8.0.320 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Introduction
- Prerequisites
- Additional Prerequisites for Azure RedHat OpenShift (ARO)
- Considerations for configuring cluster or adding nodes to an existing cluster
- Creating multiple InfoScale clusters
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Removing and adding back nodes to an Azure RedHat OpenShift (ARO) cluster
- Installing Veritas InfoScale on Kubernetes
- Introduction
- Prerequisites
- Installing Node Feature Discovery (NFD) Operator and Cert-Manager on Kubernetes
- Downloading Installer
- Tagging the InfoScale images on Kubernetes
- Applying licenses
- Considerations for configuring cluster or adding nodes to an existing cluster
- Creating multiple InfoScale clusters
- Installing InfoScale on Kubernetes
- Undeploying and uninstalling InfoScale
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- CSI plugin deployment
- Raw block volume support
- Static provisioning
- Dynamic provisioning
- Resizing Persistent Volumes (CSI volume expansion)
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Using InfoScale with non-root containers
- Using InfoScale in SELinux environments
- CSI Drivers
- Creating CSI Objects for OpenShift
- Creating ephemeral volumes
- 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 <InfoScale namespace>.
On a Kubernetes cluster, run kubectl get infoscalecluster <InfoScale namespace>.
Review output as follows:
NAME NAMESPACE VERSION STATE AGE infoscalecluster-dev <InfoScale namespace> <current version> Running 24h
The cluster state must be 'Healthy'.
On an OpenShift cluster, run oc get infoscaleclusters.infoscale.veritas.com infoscalecluster-dev <InfoScale namespace> -ojsonpath='{.status.clusterState}{"\n"}' Healthy.
On a Kubernetes cluster, run kubectl get infoscaleclusters.infoscale.veritas.com infoscalecluster-dev <InfoScale namespace> -ojsonpath='{.status.clusterState}{"\n"}' Healthy.
System returns output as follows:
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.