admin API by default listening also on IPv6 not working in IPv4 only GKE cluster

[dandynaufaldi]

Per the changes done on #986 admin API now by default will listen on both 0.0.0.0 (IPv4) and [::] (IPv6)

This default settings doesn't work well with cluster running IPv4 only stack. We got following error from the kong proxy container

proxy nginx: [emerg] bind() to [::1]:8444 failed (99: Cannot assign requested address)

helm values

admin:
  enabled: false

*basically the same with the default values

cluster and kong

Cluster

• k8s: 1.29.1
• network stack type: IPv4

Kong

• chart version: 2.38.0

[dandynaufaldi]

btw if anyone stumbled upon similar error (proxy nginx: [emerg] bind() to [::1]:8444 failed (99: Cannot assign requested address))

you can add following env variable in the Helm values to override the Kong Admin listen config so that it won't try to bind on IPv6 address and use the IPv4 only

env:
  ADMIN_LISTEN: 0.0.0.0:8444 http2 ssl

[mpdafa]

Finally, thanks mas! several hours looking for the solution, even gpt wont help haha