Router pods scheduled to same node on HCP with SingleReplica availability policies leading to eviction loop

Solution Verified - Updated -

Issue

  • In a Hosted Control Plane (HCP) cluster where infrastructureAvailabilityPolicy set to SingleReplica, ingress router pods are repeatedly scheduled onto the same node.
  • The Ingress Operator detects this pod placement as invalid (expecting router pods to be distributed across nodes) and continuously evicts the router pods.
  • This results in an endless eviction and rescheduling loop, preventing ingress from stabilizing and causing degraded or unavailable ingress functionality.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4
  • Hosted Control Plane (HCP)

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