Description of problem: Starting in OCP 4.6 the default route is always selected for the Node's InternalIP when installing using UPI. Installation has multiple network interfaces configured at install time. In OCP 4.5 the expected interface was selected which was the first interface immediately after loopback in `ip addr` listing. Version-Release number of selected component (if applicable): 4.6.1 How reproducible: Each time. Actual results: InternalIP for Node is incorrectly selected. Expected results: Either matching behavior in 4.5 where first interface is selected or having option to choose interface at install time.
Interface listing in 'ip addr' depends on kernel device enumeration order which is not stable and can change. Kubelet (or a cloud provider) is responsible detecting the node's IP address and posting to the apiserver. If you need a specific interface listed as the node's InternalIP then you need to pass specific options to kubelet to tell it which interface to use. See https://bugzilla.redhat.com/show_bug.cgi?id=1872632 for a variation of this problem (on bare-metal installs).
> If you need a specific interface listed as the node's InternalIP then you need to pass specific options to kubelet to tell it which interface to use. Yeah, the main concern is that in OCP 4.5 and earlier, looks like the kubelet picked up the InternalIP automatically. But, in 4.6 and later, the runtime-cfg sets its via a kubelet arg. Runtime-cfg picks the IP based on default route (different behavior than before).
*** This bug has been marked as a duplicate of bug 1949827 ***