Installing and configuring InfoScale DR Manager on Kubernetes

To deploy Disaster Recovery (DR) for InfoScale on Kubernetes, administrators must ensure InfoScale pods are operational and all Persistent Volume Claims (PVCs) are in a "Bound" or "Terminating" state. A load balancer—such as MetalLB or a native cloud provider equivalent—is required on all participating clusters to facilitate resilient cross-cluster communication via designated Virtual IP addresses. Furthermore, users must prepare specific network and identification data for Global Cluster Membership (GCM) and Data Replication custom resources, while ensuring no stale DR-related Custom Resources remain on the clusters.

The installation process involves creating a dedicated Storage Class and PVC on both primary and secondary clusters to support metadata backup and restoration. Administrative access is established by applying specific RBAC roles and ClusterRoleBindings. Following this, the InfoScale DR Manager deployment is configured by updating the image repository path and applying the controller manifests.