InfoScale™ 9.0 Support for Containers - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Arctera InfoScale™ on OpenShift
- Installing Arctera InfoScale™ on Kubernetes
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing InfoScale DR on OpenShift
- Installing InfoScale DR on Kubernetes
- TECHNOLOGY PREVIEW: 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 can result in data corruption. (4052704) | If you want to add a new PVC to an existing namespace
|
If data replication is configured and Volume is mounted only on a slave node, Volume resize operation (vxresize) fails with an error message 'file system is not mounted'. (4047378) | 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 Arctera Technical support. |