Kong Ingress returns 500 error after 5 min about kubernetes-ingress-controller HOT 3 OPEN

@javiramos1 Please confirm the version of your KIC and Kong gateway separately. The version 3.2 provided seems to be the version of Kong gateway.
You can use the following command to get the image used for Ingress controller and Kong gateway

kubectl get pods -n <ns> -l app.kubernetes.io/name=kong -o jsonpath={.spec.containers[*].image}

Also, konghq.com/send-timeout is not a supported annotation and Kong service does not have a send_timeout attribute. You can set konghq.com/connect-timeout or konghq.com/write-timeout: https://docs.konghq.com/kubernetes-ingress-controller/latest/reference/annotations/#konghqcomconnect-timeout. However, if your KIC version is below 2.8, they are not supported.

from kubernetes-ingress-controller.

Hi, thanks for the reply. I will update the annotations and remove send-timeout.

We are using kong/kubernetes-ingress-controller:2.9 thanks!

from kubernetes-ingress-controller.

@javiramos1 Can you please provide the further information for us to triage?

• The manifests of relevant Ingresses and Services
• The behavior of your backend services (Do they just receive requests and hang on the connection but writes nothing to the response?)
  BTW, the issue is also possible caused by AWS NLB's idle timeout on TCP connections. I found an article to tell about such example: https://medium.com/tenable-techblog/lessons-from-aws-nlb-timeouts-5028a8f65dda and the related document here https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout

from kubernetes-ingress-controller.