Arctera InfoScale™ for Kubernetes 8.0.400 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Arctera InfoScale on OpenShift
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Arctera InfoScale on Kubernetes
- Tagging the InfoScale images on Kubernetes
- Installing InfoScale on Kubernetes
- Installing Arctera InfoScale on RKE2
- Configuring KMS-based encryption on an OpenShift cluster
- Configuring KMS-based encryption on an 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
- Troubleshooting
Limitations
Following are the functional limitations due to external factors.
Table: Limitation description and workaround
Description | Workaround |
---|---|
Users can create a maximum of 32 snapshots for a volume. (VIKE-4605) | 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. |
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 the InfoScale cluster with the new coordination points. |
During migration of an application or 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 |