From 2bdf08a9c0851a3048f06007da06cfdf62cbf1c4 Mon Sep 17 00:00:00 2001 From: Ngairangbam Mili Date: Wed, 25 Sep 2024 04:10:30 +0000 Subject: [PATCH] OAM address change additional clarifications required - related to certificates Change-Id: I138e5dcd97fd5f1ae73041e4996af4ad498f0cff Signed-off-by: Ngairangbam Mili --- ...changing-the-oam-ip-configuration-using-horizon.rst | 7 +++---- ...changing-the-oam-ip-configuration-using-the-cli.rst | 10 ++++------ 2 files changed, 7 insertions(+), 10 deletions(-) diff --git a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst index c2d5b7e8b..357ecab5f 100644 --- a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst +++ b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst @@ -22,10 +22,9 @@ interface or the CLI. You can use IPv4 or IPv6 addresses. be required. In addition, |VNC| console access to worker-node hosts is interrupted until the hosts are locked and unlocked. - Once the |OAM| IP addresses are changed, any existing server certificates - (ssl, docker_registry, OpenStack etc.) that have the old |OAM| IP - addresses in their |SANs| must be updated with new certificates reflecting - the new addresses. + The registry and SSL certificates will automatically update the |OAM| + addresses in their |SANs|. However, any optional applications must have + their certificate |SANs| updated manually. .. note:: If you are running docker proxy on your system, you need to change the diff --git a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst index 024ba3545..d03d9ca5d 100644 --- a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst +++ b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst @@ -24,11 +24,9 @@ Horizon Web Interface. You can use IPv4 or IPv6 addresses. settings may also be required. In addition, |VNC| console access to worker-node hosts is interrupted until the hosts are locked and unlocked. - Once the |OAM| IP addresses are changed, any existing server certificates - (ssl, docker_registry, OpenStack etc.) that have the old |OAM| IP addresses - in their |SANs| must be updated with new certificates reflecting the new - addresses. For more information, see :ref:`Install/Update Local Registry - Certificates `. + The registry and SSL certificates will automatically update the |OAM| + addresses in their |SANs|. However, any optional applications must have + their certificate |SANs| updated manually. To view the existing |OAM| IP configuration, use the following command. @@ -121,4 +119,4 @@ OAM IP, using the following steps: :ref:`Default Firewall Rules ` - :ref:`Modify Firewall Options ` \ No newline at end of file + :ref:`Modify Firewall Options `