Veritas InfoScale™ for Kubernetes Environments 8.0.200 - 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
Limitations
Following are the functional limitations due to external factors.
Table: Limitation description and workaround
Description | Workaround |
---|---|
When DataReplication Custom Resource (CR) is configured for a namespace, adding a new PVC to this namespace or deleting an existing PVC from this namespace is not supported. (4052704) | None |
When DataReplication for DR is configured for a Galera 3 pod cluster, VVR performs a full synchronization instead of a smartsync (4051639) | None. Wait for initial full synchronization to complete before triggering the migration. |
Remove node is not supported for InfoScale on OpenShift or Kubernetes. (4044647) | To remove node, contact Veritas Technical support. |
InfoScale modules fail to load on Kubernetes if SELinux is enabled on the worker nodes. (VIKE-1028) | Perform the following steps
|
Replacing disks or replacing coordination points without unconfiguring fencing is not supported. (VIKE-2563) | Reconfigure InfoScale cluster with the new coordination points. |