Apply service timeout

[mbaylet]

Hi,

I struggled to get my timeout configuration applied on the latest KIC (2.8) based on the current documentation:
https://docs.konghq.com/kubernetes-ingress-controller/latest/references/annotations/#konghqcomread-timeout
here is my service anotation:

apiVersion: v1
kind: Service
metadata:
  name: MyApp
  annotations:
    konghq.com/connect-timeout: "180000"
    konghq.com/write-timeout: "180000"
    konghq.com/read-timeout: "180000"

Unfortunately, even with this settings, my request hit a 504 timeout after 60 seconds.
My ingress is managed by kong and the service is fully reachable.
Do i miss something ?

[fffonion]

cc @Kong/team-k8s could you help on this question?

[rainest]

If you check the admin API, what is the actual read_timeout shown on the generated Kong service? If that looks correct, something is going wrong in the gateway code, but I can't think of any reason offhand that timeout setting wouldn't work.

If it does not match the timeout set in the annotation, do the controller logs show any errors indicating it failed to apply configuration? Limitations in the way DB-less configuration works mean that unrelated errors can block application of configuration updates that are otherwise valid, e.g. if you have a misconfigured Ingress somewhere it can prevent your Service changes from taking effect. If that's the case, controller logs will show an error indicating the name of the problem Kong resource (which will include the namespace and name of the associated Kubernetes resource) and why it's rejected.

If you're seeing neither of those (there are no controller log errors, but the Kong service does not have the expected read_timeout), double-check your controller image version. Those annotations are fairly recent additions, so if you are unexpectedly running on an older controller version, they would be ignored.

[gagarinfan]

Hey @mbaylet. Did you manage to fix it and apply custom timeouts on the Service level? I'm struggling with the same issue. I'm running kong chart in DB-less mode, version: 2.39.3

[mloskot]

FYI, I have tested the Kubernetes Service annotations and those seem to work for me, see my whole story here:

• How to globally set NGINX proxy timeouts on Kong via KIC kubernetes-ingress-controller#6662 (comment)