KIC is failing after upgrading to 3.4 from 2.12

[sathya15992]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After upgrading KIC version from 2.12 to 3.4, Ingress controller container is not starting and restarting multiple times. We can see connection refused for liveness and readiness probe. Please help to resolve this issue.

Expected Behavior

After upgrading, container should up and running.

Steps To Reproduce

Just upgraded via helm.

Kong Ingress Controller version

3.4

Kubernetes version

1.32

Anything else?

No response

[randmonkey]

@sathya15992 Can you please provide the logs?
There are some breaking changes from 2.12 to 3.x, so direct upgrade may cause issues and migration may needed. see: https://developer.konghq.com/kubernetes-ingress-controller/faq/upgrading-ingress-controller/#upgrade-to-kong-ingress-controller-3-0