starlingx/docs
Code Issues Proposed changes

OAM address change additional clarifications required - related to certificates

Browse Source 
Change-Id: I138e5dcd97fd5f1ae73041e4996af4ad498f0cff
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2024-09-25 04:10:30 +00:00
parent f10e972180
commit 2bdf08a9c0
2 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst
View File

@ -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

10
doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst
View File

@ -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 <installing-updating-the-docker-registry-certificate>`.
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 <security-default-firewall-rules>`
:ref:`Modify Firewall Options <security-firewall-options>`
:ref:`Modify Firewall Options <security-firewall-options>`