No timeout or 2min timeout for services to acknowledge there are no endpoints

Solution Verified - Updated -

Issue

Openshift services may take up to 2 minutes to result in connection timeout when the endpoints are removed.
This may create problems for some frontend applications to know when their backend applications are down, since inside Openshift usually pod to pod communication is done through their Kubernetes Services.

Environment

Openshift Container Platform 4.1 and 4.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In