Configuring Global Cluster Membership (GCM)

Last published : Jun 12, 2026
With Global Cluster Membership (GCM), you can define membership of clusters for disaster recovery. The GCM CR must be configured and applied on all clusters. When configured, the Global Cluster Membership forms a logical notion called 'Global Cluster' with all underlying clusters as 'Member Clusters'. Member clusters are Kubernetes clusters providing disaster recovery capabilities to application components. To provide DR, these member clusters
  1. Send heartbeats with each other periodically.
  2. Exchange information like state, configuration, operation.
  3. Perform/participate in operation like migration.
Complete the following steps
  1. Edit /YAML/DR/SampleGlobalClusterMembership.yaml as under
    apiVersion: infoscale.veritas.com/v1
    kind: GlobalClusterMembership
    metadata:
      name: global-cluster-membership
    spec:
      \# Local cluster name in the global membership
      localClusterName: <Local cluster(primary) where
                                          you want to apply this YAML>
      globalMemberClusters:
          \# Cluster ID of each member of global cluster membership
        -  clusterID: <ID of the cluster for which you want a DR backup>
          \# Address Used For Communicating With Peer Cluster's DR Controller
          drControllerAddress: "<Load balancer IP address or haproxy
                                                 of the local cluster>"
          \# Port used for DR controller
          drControllerPort: "<Load balancer port number>"
        -  clusterID: <ID of the Cluster to be used for a backup>
          drControllerAddress: "<Load balancer IP address or haproxy
                                                    of the DR site>"
          drControllerPort: "<Load balancer port number>"
      \# If heartbeat with peer cluster missed more than CounterMissTolerance
           times, then cluster will be moved to FAULTED state

      counterMissTolerance: 5
      globalClusterOperation: "none"
      \# Application metadata backup sync frequency to DR site(s) in minutes
      metadataBackupInterval: 15
      \# Refresh data replication status after specified minutes
      datarepRefreshStatusFrequency: 10
      \# Include cluster-scoped Custoum Resource Definitions (CRDs)
                          in disaster recovery plan backup
      backupClusterScopeCRD: true
    Note: Do not enclose the parameter values in angle brackets(< >) . For example, if 8334 is the Load balancer port number; enterdrControllerPort: "8334"fordrControllerPort: "
    1. Run the following command on the master node of the source cluster.
    kubectl apply -f /YAML/DR/SampleGlobalClusterMembership.yaml
    1. Edit another instance of /YAML/DR/SampleGlobalClusterMembership.yaml to add DR site as under
    apiVersion: infoscale.veritas.com/v1
    kind: GlobalClusterMembership
    metadata:
      name: global-cluster-membership
    spec:
      \# Local cluster name in the global membership
      localClusterName: <Local cluster (secondary) where
                                          you want to apply this YAML>
      globalMemberClusters:
          \# Cluster ID of each member of global cluster membership
        -  clusterID: \<ID of the cluster for which you want a DR backup\>
          \# Address Used For Communicating With Peer Cluster's DR Controller
          drControllerAddress: "<Load balancer IP address or haproxy
                                                 of the local cluster>"
          \# Port used for DR controller
          drControllerPort: "\<Load balancer port number\>"
        -  clusterID: \<ID of the Cluster to be used for a backup\>
          drControllerAddress: "<Load balancer IP address or haproxy
                                                  of the DR site>"
          drControllerPort: "\<Load balancer port number\>"
      \# If heartbeat with peer cluster missed more than CounterMissTolerance
                       times, then cluster will be moved to FAULTED state

      counterMissTolerance: 5
      globalClusterOperation: "none"
      \# Application metadata backup sync frequency to DR site(s) in minutes
      metadataBackupInterval: 15
      \# Refresh data replication status after specified minutes
      datarepRefreshStatusFrequency: 10
      \# Include cluster-scoped Custoum Resource Definitions (CRDs)
                                  in disaster recovery plan backup
      backupClusterScopeCRD: true
Related information