[RHOCP 4] NMstate configuration is causing issue with IPAddress ordering on Egress Nodes

Solution Verified - Updated -

Issue

  • Updating DNS using Kubernetes NMState results in changing the ordering of the IP addresses to alphanumerically sorted IP addresses on the Egress node.

  • When Kubernetes NMState is configured for updating the DNS server, an issue is observed on Egress Nodes, the ordering of the IP Addresses changes, and Node IPs are sorted by alphanumeric order.

  • For instance, consider 10.xx.xx.17 is the egress IP assigned to a node, and 10.xx.xx.2 is the actual host IP. In this case, 10.xx.xx.17 will take precedence over the host IP 10.xx.xx.2 if sorted alphanumerically. Ideally, the host IP should not change to an egress IP.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Kubernetes NMState

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content