Understanding Replication CR Workflow

Replication Plug-in for Containers Installation and User Guide

Version
3.18.x
Audience
anonymous
Part Number
MK-92ADPTR155-10
ft:lastEdition
2026-07-07

When you create a Replication CR, several related CRs are generated automatically in a defined sequence. The following table outlines these CRs and their order of creation, which can help you understand the workflow and assist in troubleshooting.

Site CRD name What the CR represents The order in which the resource are ready
Primary Replication A Universal Replicator pair or TrueCopy pair created by Replication Plug-in for Containers. This is physically the same as the Replication at the secondary site. 5
LocalVolume A Universal Replicator or TrueCopy P-Vol created by users. This is physically the same as the RemoteVolume at the secondary site. 1
RemoteVolume A Universal Replicator or TrueCopy S-Vol created by Replication Plug-in for Containers. This is physically the same as the LocalVolume at the secondary site. 4
Secondary Replication A Universal Replicator pair or TrueCopy pair created by Replication Plug-in for Containers. This is physically the same as the Replication at the primary site. 5
LocalVolume A Universal Replicator or TrueCopy S-Vol created by Replication Plug-in for Containers. This is physically the same as the RemoteVolume at the primary site. 2
RemoteVolume A Universal Replicator or TrueCopy P-Vol created by users. This is physically the same as the LocalVolume at the primary site. 3

When you run the kubectl create -f hspc_v1_replication.yaml command, the above CRs are created in the following order:

  1. A LocalVolume CR in the primary site is created and becomes true when a PVC specified in hspc_v1_replication.yaml file exists.
  2. A LocalVolume CR in the secondary site is created and becomes true when a PVC is successfully created.
  3. A RemoteVolume CR in the secondary site is created and becomes true when Replication Plug-in for Containers can confirm existence of the PVC in the primary site.
  4. A RemoteVolume CR in the primary site is created and becomes true when Replication Plug-in for Containers can confirm existence of the PVC in the secondary site.
  5. Replication CRs in both primary and secondary site becomes Pair when both Replication Plug-in for Containers can confirm Universal Replicator or TrueCopy pair creation and initial data copy.

    You will see the following output when all CRs are successfully created:

    # kubectl get localvolume
    NAME                 READY   AGE
    replication-sample   true    6d20h
    
    # kubectl get remotevolume
    NAME                 READY   AGE
    replication-sample   true    6d20h
    
    # kubectl get replication
    NAME                 STATUS   DESIREDSTATE   OPERATION  AGE
    replication-sample   Pair      none              none         6d20h