Veritas InfoScale™ for Kubernetes Environments 8.0.300 - 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
- 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
- Migrating applications to InfoScale
- Troubleshooting
Limitations
Following are the functional limitations due to external factors.
Table: Limitation description and workaround
Description | Workaround |
|---|---|
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. |
During migration of an application or just before takeover of an application, if PVCs and PVs are added to its namespace; the PVCs and PVs might not successfully restore on the secondary site. | None |