From 5c54633d73d98bd660cd72c78357597e5b647af8 Mon Sep 17 00:00:00 2001 From: Matthew Montopoli Date: Thu, 3 Jul 2025 13:53:00 +0000 Subject: [PATCH] Update rehoming-subcloud documentation for CC ssl_ca expiring certificates (dsr8mr2+, dsr8mr3, dsr10, dsr10m, r9, r10) Change-Id: I7ba27b2bf712794219d53e32534a915af9959287 Signed-off-by: Matthew Montopoli (cherry picked from commit 552f2ef4ab6a5b7412db9075c4c596c7ab93f922) --- doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst b/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst index 6493f9bc3..17d888449 100644 --- a/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst +++ b/doc/source/dist_cloud/kubernetes/rehoming-a-subcloud.rst @@ -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 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:: The rehoming playbook does not work with freshly installed/bootstrapped