Cluster upgrade causes Ingress VIP getting attached to two nodes at once

Solution Verified - Updated -

Issue

  • After cluster upgrade from OpenShift v4.10 to v4.11 traffic is routed to worker nodes where default router pods is not present causing Ingress, Authentication and Console cluster operator going into degraded state with connection refused error.
  • After upgrading to OpenShift v4.11 Ingress VIP gets attached to multiple nodes at same time.
  • After an upgrade to v4.11, more than one node owns the API VIP or the kube-apiserver VIP

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.10
    • 4.11
    • 4.12
    • 4.13
  • IPI installation method

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