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
Limitations
Following are the functional limitations due to external factors.
Table: Limitation description and workaround
Description | Workaround |
---|---|
Storage expansion by adding disks to the node (scale up) is not supported. (4046551) Note: This limitation is applicable to Direct Attached Storage (DAS) only. | Reboot the entire cluster after manually adding disks to a node. Then add new disks to the disk group manually when the cluster comes up. |
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. |
Disaster Recovery (DR) is not supported for PVCs with 'encryption' set to 'true' in their SCs. | None |
Migration/Takeover of applications requiring Security Context Constraints is not supported. (VIKE-1264) | Manually copy the SCC yaml files from the source to the target cluster. |
When a VolumeSnapshot object is created, the free size of a Disk group is not updated in the database till some operation is performed on the PVC object in the cluster. (VIKE-1527) | None |