starlingx/docs
Code Issues Proposed changes

Update rehoming-subcloud documentation for CC ssl_ca expiring certificates (dsr8mr2+, dsr8mr3, dsr10, dsr10m, r9, r10)

Browse Source 
Change-Id: I7ba27b2bf712794219d53e32534a915af9959287
Signed-off-by: Matthew Montopoli <matthew.montopoli@windriver.com>
(cherry picked from commit 552f2ef4ab)
This commit is contained in:
Matthew Montopoli
2025-07-03 13:53:00 +00:00
committed by Juanita-Balaraj
parent 07e4ea00a7
commit 5c54633d73
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -10,6 +10,14 @@ multiple system controllers are being consolidated into a single system
controller, you can add already deployed subclouds to a different system controller, you can add already deployed subclouds to a different system
controller using the rehoming playbook. controller using the rehoming playbook.
.. note::
Before performing rehoming, inspect the "From" Central Cloud as well as the
"To" Central Cloud active controllers for ssl_ca certificate expiration.
If there are soon-to-expire ssl_ca certificates in either Central Cloud system, they
need to be updated. This will prevent triggering 500.200 alarms
after rehoming in the rehomed subclouds.
.. note:: .. note::
The rehoming playbook does not work with freshly installed/bootstrapped The rehoming playbook does not work with freshly installed/bootstrapped