Quarkus application slow to start in an OpenShift pod

Solution Verified - Updated -

Issue

A Quarkus application pod is slow to come to readiness, compared with the way it behaves in desktop testing. For example, an application running on bare metal might start in two seconds, but require thirty seconds as an OpenShift pod.

Environment

  • Red Hat build of Quarkus
    • All versions

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