OCP Service does not scale up after idling

Solution Verified - Updated -

Issue

  • When we idle (oc idle) a Service it gets scaled down to 0 as expected, but after calling the Route it doesn't scale up to 1.
  • Calling an idled applications results in a HTTP 503 error on OpenShift Container Platform 4.6.

Environment

  • OpenShift Container Platform 4.6

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