#Global Cluster Disaster Recovery

This page is the disaster recovery entry point for a global cluster that runs on Immutable Infrastructure. Deploy-time disaster recovery configuration is part of the global cluster installation procedure.

#Deployment Procedure

Use Optional Disaster Recovery Deployment in the installation guide when you create the primary and standby global clusters.

That deployment procedure is the authoritative source for the installation-time DR configuration, including:

• Primary and standby clusters use the same Kubernetes API server encryption provider configuration.
• The etcd server certificate SAN list includes both the primary and standby control plane VIPs and the Platform Access Address.
• Huawei DCS deployments reference the shared encryption provider Secret from DCSCluster.spec.encryptionProviderConfigRef.
• VMware vSphere deployments write the same /etc/kubernetes/encryption-provider.conf file through KubeadmControlPlane.spec.kubeadmConfigSpec.files.
• Huawei Cloud Stack deployments write the same /etc/kubernetes/encryption-provider.conf file through KubeadmControlPlane.spec.kubeadmConfigSpec.files.
• VMware vSphere and Huawei Cloud Stack create the dcs-import-extra-resources ConfigMap before installer import so the installation can preserve provider-specific resources. The name keeps the dcs prefix for historical installer compatibility. Huawei DCS uses the built-in provider resource migration unless extra resources must be imported.
• The primary cluster installs global-etcd-sync with the standby cluster connection values after both installations succeed.

#Operational Scope

After the primary and standby clusters are installed, operate DR as a separate lifecycle process. Keep the installation manifests aligned with the installation guide, then use an approved operations runbook for the following tasks:

• Verify etcd-sync health and replication lag.
• Verify that the standby cluster can decrypt Kubernetes Secrets created on the primary cluster.
• Validate the primary and standby control plane VIPs and the platform access path before a planned failover.
• Execute failover and failback with an approved operations procedure.
• Reconcile provider-specific resources after a failover.

#Provider Notes

#See Also

For traditional-operating-system global cluster disaster recovery, see Global Cluster Disaster Recovery.

For installation and upgrade of the global cluster on Immutable Infrastructure, see:

• Installing the global Cluster
• Upgrading the global Cluster