Health check probes fail with i/o timeout in Service Mesh 3 Ambient mode when NetworkPolicies are applied

Solution Verified - Updated -

Issue

  • Pods enrolled in Red Hat Service Mesh (OSSM) Ambient mode fail Startup, Readiness, or Liveness probes.

  • oc get events -n <namespace> shows i/o timeout events, and the affected pod enters the CrashLoopBackOff state.

    Warning   Unhealthy               pod/http-deployment-xxx-xxx   Startup probe failed: dial tcp 10.x.x.x:8080: i/o timeout
Normal    Killing                 pod/http-deployment-xxx-xxx   Container http-reader failed startup probe, will be restarted

  • The issue persists even when routingViaHost: true is correctly set.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Service Mesh (OSSM)
    • 3

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