Kong pod doesnt start up after cluster restart : needs Kong 3.9

[alahane-techtel]

What happened?

The issue is:

Kong/kong#13730 (comment)

We are using latest kubernetes-dashboard which inturn uses kong.
Whenever the cluster nodes are restarted (may it be my windows machine running docker-desktop with single node k8s, or may it be our 3 node dev env k8s cluster running on latest Ubuntu and containerD), I get this same issue:

nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use)

Once I delete the kong pod, all comes back to normalcy. Will appreciate a fix for this.

It is already fixed in Kong. Hence Kong should be updated to 3.9 to fix the issue.

For now, we can work around by overriding the Kong version as this:

helm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard \
    --create-namespace \
    --namespace kubernetes-dashboard \
    --set kong.image.repository=kong \
    --set kong.image.tag="3.9.0"

What did you expect to happen?

Whenever the cluster nodes are restarted (may it be my windows machine running docker-desktop with single node k8s, or may it be our 3 node dev env k8s cluster running on latest Ubuntu and containerD), we should still be able to access k8s-dashboard.

How can we reproduce it (as minimally and precisely as possible)?

Just restart all the k8s nodes.

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.10.4

Kubernetes version

1.30.5

Dev environment

No response