Jira https://issues.redhat.com//browse/OCPBUGS-36499 introduced a backport in 4.15.22 on how to setup internal OVN networks, however the documentation is outdated and on one part is incorrect.

From what I can see in the PR, the backport made CNO API the same as we have now for OCP 4.16 allowing the change of the transit and masquerade networks. However there were some changes in the structure of the networ.operator.openshift.io CR which is also not reflected in 4.15 documentation which can lead to problems configuring it.

Documents affected are:

https://docs.openshift.com/container-platform/4.15/networking/cluster-network-operator.html
https://docs.openshift.com/container-platform/4.15/rest_api/operator_apis/network-operator-openshift-io-v1.html#spec-defaultnetwork-ovnkubernetesconfig

And all docs related with installation of all platforms with network costumizations like the example below for bare metal:

https://docs.openshift.com/container-platform/4.15/installing/installing_bare_metal/installing-bare-metal-network-customizations.html#nw-operator-cr-cno-object_installing-bare-metal-network-customizations

In these installation docs we probably should make a warning about the coded network address for this transit switch subnet the same we have for the join network 100.64.0.0/16

Another point is that the gatewayConfig section is incomplete missing the new fields ipv4 and ipv6.

I made this Jira for 4.14 because we are making the same backports to this version. Currently being worked here - https://issues.redhat.com//browse/OCPBUGS-38440

Probably good thing to start preparing the docs change as well.

Let me know in case you prefer multiple Jiras or if you are okay to have this one for all of this

    OCP 4.14 and 4.15