starlingx
/
docs
Code Issues Proposed changes

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

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 d012c75be5
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -614,6 +614,14 @@ The table below lists the operations that can/cannot be performed on the protect
| | | |
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
.. note::
After migrating the subcloud, ``kube-rootca_sync_status`` will be
``out-of-sync``. To update the root |CA| certificate of the subcloud, run
the :command:`dcmanager kube-rootca-update-strategy` command. However, if
you update the certificate and migrate the subcloud back to the
primary site, then the certificate needs to be updated again.

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

@ -229,6 +229,12 @@ 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`` will
be ``out-of-sync``. To update the Kubernetes Root |CA| certificate of the subcloud,
use the :command:`dcmanager kube-rootca-update-strategy` command.
.. rubric:: Error Recovery
If the subcloud rehoming process begins successfully, (status changes to