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
Prerequisites
InfoScale pods must be configured on the clusters.
Load balancer must be installed and configured. If you choose to install Metallb as the load balancer, steps are listed in
Installing DR Operator
.Be ready with the following information for every member cluster
GlobalClusterMembership: Virtual IP address and a port for each member cluster in GCM. This information is captured in GCM custom resource.
Data Replication: Virtual IP address, port, netmask and network interface (NIC) required for each cluster to be specified in DataReplication CR. This information is exclusive for a DataReplication CR and is used to configure Arctera Volume Replicator .
Ensure that stale Custom Resources (CR) and Custom Resource Definitions (CRD) related to DR do not exist on the clusters.
Storage class used for the Application persistent storage must be based on InfoScale CSI with
RECLAIMPOLICY = Retain
.To know RECLAIMPOLICY, run the following command and verify the output
kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE csi-infoscale-sc org.veritas.infoscale Retain Immediate
ALLOWVOLUMEEXPANSION AGE true 49d
Optionally if you want to configure DNS resource, DNS key and DNS private key. To know how to obtain keys, see https://www.veritas.com/content/support/en_US/ doc/129694359-129694362-0/uxrt-731_id-SF1J0175244-129694362 .