The "api-int" address is failing to resolve in OpenShift 4, but it is not a DNS requirement

Solution Verified - Updated -

Issue

  • After a change in the DNS/DHCP environment network, the nodes become NotReady after a reboot.
  • We can observe the "api-int" address failing to resolve, but the requirements for the platform are only "api" and "*.apps".
  • The static coredns pod is crash-looping.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • Verified in version 4.15 and 4.16, but may happen in other versions.
  • Verified in the Nutanix platform, but may happen in any platform with static coredns pods.

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