Disabling the connection

Disable the connection between Hub and Spoke.

About this task

In Hub and Spoke, there is a connection CR in each cluster that represents the connection to the another(remote) cluster. Delete connection CR in the Spoke or Hub. If the network is down, then use either method 1 or method 2 to manually delete the connection CR in another cluster also.

Important: Disabling a spoke connection results in the unassignment of policies from spoke applications, and no new backups are initiated subsequently. Custom Resources (CRs) of applications without backups are deleted, and these applications no longer appear in the user interface.

Method 1: Using command line or command prompt

Procedure

  1. In the Spoke, use the following command to get all the connection CR: 
    oc get connection -n <fusion-namespace> -o=custom-columns='NAME:.metadata.name,ClusterName:.metadata.annotations.connection\.isf\.ibm\.com/cluster-name'
    Example command: 
    oc get connection -n ibm-spectrum-fusion-ns -o=custom-columns='NAME:.metadata.name,ClusterName:.metadata.annotations.connection\.isf\.ibm\.com/cluster-name'
    Example output:
    NAME                    ClusterName
connection-44ae8529aa   cp4d-vpc-98b7318c91b01bd72490e80cc2328915-0000.us-east.containers.appdomain.cloud
  2. Check the ClusterName in connection CR, and delete the connection CR which has the same ClusterName with Hub: 
    oc delete connection <connection-name>  -n <fusion-namespace>
    Example command:
    oc delete connection connection-44ae8529aa -n ibm-spectrum-fusion-ns

Method 2: By using OpenShift Container Platform console

Procedure

  1. Log in to OpenShift Container Platform console.
  2. Go to Administration > CustomResourceDefinitions > connections.application.isf.ibm.com > Instances.
  3. Get the connection instance whose cluster name in the annotation is the same as the hub cluster name.
  4. Delete this connection instance.