Liveness probe exec check fails where HTTP and TCP work as exptected

Solution Verified - Updated -

Issue

  • When exec checks are used in a liveness probe the checks fail nearly every time, and in some cases resulting in the pod going into CrashLoopBackOff status. If the liveness check is removed, or a different type is used (HTTP or TCP) the pod operates as expected.

Environment

  • OpenShift Container Platform (OCP) 4.3.5

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