Kong returns 503 error to api-client due to failure in DNS resolution of upstream service about kong

[fairyqb]

This is a problem with your DNS server and has nothing to do with KONG.

[hungran]

I believed xxx.yyy here is public FQND of the site, however the upstream inside the k8s environment should be k8s-servicename.k8s-namespace.svc.cluster.local
so it should be Kong issue

[hungran]

actually we also faced same issue when using Kong inside Azure Kubernetes and service mesh linkerd
https://linkerd.io/2.14/tasks/using-ingress/#kong

even we found and somehow can be work around by hardcode the header l5d-dst-override by: servicename.k8snamespace.svc.cluster.local:serviceport

however would be better if Kong have a way to recognize and solve the DNS of k8s svc that we can transform the l5d-dst-override at our side

[nowNick]

Hey @naveen-thangamalayan!

Thank you for reporting this issue!

Would it be possible for you to upgrade to a newer Kong version? There were a couple of fixes related to DNS in newer versions.
Officially 3.1 is not in full support any longer (https://docs.konghq.com/gateway/latest/support-policy/)

@hungran - are you using the same Kong verision?

[chronolaw]

@naveen-thangamalayan , do you still have this issue after kong gateway version bump?

[github-actions]

This issue is marked as stale because it has been open for 14 days with no activity.

[github-actions]

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look
our pledge to the community
for more information.

Sincerely,
Your Kong Gateway team