starlingx
/
docs
Code Issues Proposed changes

Merge "Add a note informing that the k8s rootca must be updated after a subcloud rehome operation (dsr8mr3)"

This commit is contained in:
Zuul 2024-04-24 14:01:42 +00:00 committed by Gerrit Code Review
parent be3c3dd715 59f2351b9b
commit 7baf37eba7
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/dist_cloud/kubernetes/configure-distributed-cloud-system-controller-geo-redundancy-e3a31d6bf662.rst
View File

@ -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.

8
doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst
View File

@ -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