-
Bug
-
Resolution: Done
-
Normal
-
4.17.z, 4.16.z, 4.18.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
5
-
Moderate
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 268, OSDOCS Sprint 269
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the following documentation: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/installing_on_bare_metal/installer-provisioned-infrastructure#enabling-a-provisioning-network-after-installation_ipi-install-post-installation-configuration https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/installing_on_bare_metal/user-provisioned-infrastructure#creating-manifest-file-customized-br-ex-bridge_installing-bare-metal There is no note about the Creating a manifest object that includes a customized br-ex bridge feature are currently only supported for Baremetal platform, which might cause confustion. It is necessary to add the note to the above documentation as well as the release note to clarify the limitation. Additionally, in the following note in the above first documentation, it is necessary to add more details like "You cannot change IP address post-installation, always include the masquerade address for br-ex in the NNCP CR." Important As a post-installation task, you can configure most parameters for a customized br-ex bridge that you defined in an existing NNCP CR, except for the IP address.