Gateway API stops working after restart of single node 'cluster' #32596
Labels
kind/bug
This is a bug in the Cilium logic.
kind/community-report
This was reported by a user in the Cilium community, eg via Slack.
need-more-info
More information is required to further debug or fix the issue.
needs/triage
This issue requires triaging to establish severity and next steps.
Is there an existing issue for this?
What happened?
When I have a single node cluster, and reboot the machine, after everything has started again, gateway API isn't working correctly. Especially deploying new gateway resources. The reason seems pretty simple, at start up, cilium tries to talk to Kube API to get the gateway CRD and gets a timeout. It retries but fails to actually get the needed response. Maybe the non-existence of the CRD is cached ? It repeats for a while until it gives up
A describe of a new gateway resource just says: waiting for controller
Cilium Version
tested with:
1.15.4
1.15.5
1.16.0-pre.2
1.16.0-pre.2 has no output
Kernel Version
tested with:
6.1.0-18-amd64
Kubernetes Version
tested with: v1.29.5
Regression
No response
Sysdump
No response
Relevant log output
Anything else?
No response
Cilium Users Document
Code of Conduct
The text was updated successfully, but these errors were encountered: