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

Story: 2010852
Task: 49913

Change-Id: I90612cc123f42c7dc061c954a17c818c755b68ff
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2024-04-22 05:20:21 +00:00
parent 3049528a18
commit 59f2351b9b
2 changed files with 18 additions and 0 deletions

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.

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