This docs bug is a request to modify the documentation for 4.13 noting that it is going to be based on RHEL 9.2. 

Placing component in machine-config-operator first, but can be moved around to different group as applicable.

Primarily, it should be highlighted that in 4.13, the default network filetype is *.nmconnection keyfile formats, and no longer will create IFCFG legacy filetypes.

With OCP 4.13 changing to RHEL 9 base (https://access.redhat.com/articles/6907891) we will want to ensure some of those RHEL9 changes are documented/referenced in our OCP docs.

Below are the details regarding this upcoming change, and some highlighted possible placement locations that would logically be important to know about this change when reviewing our documentation.

Version release tracking: https://access.redhat.com/articles/6907891

#RHEL 9 changes:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality#deprecated-functionality_networking

~~~

NetworkManager stores new network configurations to /etc/NetworkManager/system-connections/ in a key-file format

Previously, NetworkManager stored new network configurations to /etc/sysconfig/network-scripts/ in the ifcfg format. Starting with RHEL 9.0, RHEL stores new network configurations at /etc/NetworkManager/system-connections/ in a key-file format. The connections for which the configurations are stored to /etc/sysconfig/network-scripts/ in the old format still work uninterrupted. Modifications in existing profiles continue updating the older files.

(BZ#1894877)

~~~

Q - What happens to clusters that already have ifcfg files configured in either machineconfigs or nmstate? 

A - These legacy files will continue to be updated and utilized (Cluster will not be impacted with an upgrade), but new default connections will be generated in *.nmconnection format, and new network configuration updates should be created as keyfile, not IFCFG moving forward. New cluster deployments should rely on *.nmconnection files for longevity.

• Add note/warning to nmstate docs section? https://56093--docspreview.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html

[IMPORTANT]

====

NetworkManager stores new network configurations to /etc/NetworkManager/system-connections/ in a key-file format

Previously, NetworkManager stored new network configurations to /etc/sysconfig/network-scripts/ in the ifcfg format. Starting with RHEL 9.0, RHEL stores new network configurations at /etc/NetworkManager/system-connections/ in a key-file format. The connections for which the configurations are stored to /etc/sysconfig/network-scripts/ in the old format still work uninterrupted. Modifications in existing profiles continue updating the older files.

(BZ#1894877)

====

• Add note/warning to machineconfig docs? https://56093--docspreview.netlify.app/openshift-enterprise/latest/post_installation_configuration/machine-configuration-tasks.html

• Add note/warning to upgrade docs? This likely should be something an administrator should consider before they upgrade to 4.13.