KIC 3.5.4 — Liveness/Readiness probes failing: dial tcp :10254: connect: connection refused

[mullasaddam]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

In Kong Ingress Controller 3.5.4, the container repeatedly fails both liveness and readiness probes:
Liveness probe failed: dial tcp :10254: connect: connection refused
Readiness probe failed: dial tcp :10254: connect: connection refused

This results in the controller going into CrashLoopBackOff.
The issue happens immediately after pod start — the controller never opens port 10254, which is the expected health endpoint. i have open the network policy for both pods still same issue and kong-proxy-server is up and running

Expected Behavior

No response

Steps To Reproduce

Kong Ingress Controller version

Environment

KIC Version: 3.5.4
(Confirmed from Docker Hub / release tags)
Image:
kong/kubernetes-ingress-controller:3.5.4
Kubernetes: eks 1.32
Helm Chart: no , manual deployment 
Kong Gateway: 3.9.1

Kubernetes version

1.32

Anything else?

No response

[randmonkey]

@mullasaddam Could you please provide the manifests to deploy KIC? I think it should be a misconfiugration in the manifests.