Service with selector removed is causing wrong haproxy.config in OpenShift Container Platform 4

Solution In Progress - Updated -


  • When removing the selector of a service exposed via route, restarting pods and adding the selector back, the haproxy.config contains invalid backend endpoints.
  • Removing the selector from a service fails to remove the backend configuration in haproxy.config of the router. This is causing specific requests to fail as they are routed to a backend that does not exist.


  • Red Hat OpenShift Container Platform (OCP) 4

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