diff --git a/doc/source/dist_cloud/kubernetes/configure-distributed-cloud-system-controller-geo-redundancy-e3a31d6bf662.rst b/doc/source/dist_cloud/kubernetes/configure-distributed-cloud-system-controller-geo-redundancy-e3a31d6bf662.rst
index d53163967..f7e064ac8 100644
--- a/doc/source/dist_cloud/kubernetes/configure-distributed-cloud-system-controller-geo-redundancy-e3a31d6bf662.rst
+++ b/doc/source/dist_cloud/kubernetes/configure-distributed-cloud-system-controller-geo-redundancy-e3a31d6bf662.rst
@@ -614,6 +614,16 @@ The table below lists the operations that can/cannot be performed on the protect
    |                                          |                                  |                                                                                                 |
    +------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
 
+.. note::
+
+    After migrating the subcloud, ``kube-rootca_sync_status`` may become
+    ``out-of-sync`` if it is not synchronized with the new system controller.
+    To update the root |CA| certificate of the subcloud, run the
+    :command:`dcmanager kube-rootca-update-strategy` command and pass the
+    ``kube-root`` |CA| cert from the new system controller. However, if you update
+    the certificate and migrate the subcloud back to the primary site, then the
+    certificate needs to be updated again.
+
 
 
 
diff --git a/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst b/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst
index 6bfc56f26..48f3b8d2f 100644
--- a/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst
+++ b/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst
@@ -229,6 +229,14 @@ There are six phases for Rehoming a subcloud:
        :start-after: rehoming-begin
        :end-before: rehoming-end
 
+.. note::
+
+    After the subcloud is rehomed and managed, ``kube-rootca_sync_status`` may
+    become ``out-of-sync`` if it is not synchronized with the new system
+    controller. To update the Kubernetes Root |CA| certificate of the subcloud,
+    use the :command:`dcmanager kube-rootca-update-strategy` command and pass the
+    ``kube-root`` |CA| cert from the new system controller.
+
 .. rubric:: Error Recovery
 
 If the subcloud rehoming process begins successfully, (status changes to