HAProxy reports 503 messages on OpenShift after enabling application security

Solution Unverified - Updated -

Issue

  • The moment we enable security for an application, probing fails with authentication and mark the instances down causing 503 errors though the application is actually up.
  • On OpenShift 3.1, the kubernetes HTTPS readiness healthcheck fails when the application is using its own CERTS. The issue was kubernetes used the ip address of the pod instead of the dns name to validate readiness check.

Environment

  • OpenShift Enterprise 2.1
  • OpenShift Container Platform 3.0+

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.