Intermittent 503 Liveness and Readiness Probe Health Check

[hvk]

The issue I hit is mentioned here (exact same issue):

Healthcheck failed on main container after integrating consul

Hi, I have Consul installed on my k8s cluster through helm, and have one service currently running with consul.hashicorp.com/connect-inject: ‘true’ Every random minutes, the main container would throw a 503 healthcheck error, leading to crashloopbackoff. Looking at kubectl describe pods, the healthcheck seems to be altered by consul to port 20300/20400, not the port 8080 described in my deployment yml. Do you know what triggers the 503 error? Looking at app logs, there’s no indication of any…