-
Notifications
You must be signed in to change notification settings - Fork 13
HTTPRoute not working with error 503 due to cointainer image cloudflare/cloudflared:2024.11.1 #202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you get the operator logs please? cloudflared just receives config from the operator via cloudflare's API, so its version shouldn't impact config |
@pl4nty, you are right; I think I've identified the error now. If I apply a single YAML with a gateway and a httproute like in the example, I get the 503 error when accessing the httproute. If I delete the gateway pod, then after it gets recreated, I can see the message in the logs with It could be that if the httproute gets created before the gateway exists, the gateway isn't able to reconcile the configuration and update.
|
I've run into a similar issue, it appears that there's a race condition between the creation of the HttpRoute resource and the configuration being applied to the tunnel. I believe the issue @pipoe2h ran into is that if you create both the Gateway and the HttpRoute at the same time then the configuration doesn't exist on first launch of the Gateway but then doesn't ever receive the configuration update with the HttpRoute configuration. Tangentially it appears that old hostname routes aren't cleaned up in Cloudflare after they've been removed. I'll open another issue for that. Happy to look into fixes over the next week! |
@pipoe2h do you have the logs from cloudflared? those controller logs indicate tunnel config was sent to the API, but may not be received by cloudflared @jseely if the gateway and route are created simultaneously, the route controller will wait 1 minute for the tunnel to exist in Cloudflare's API. after that, it should send config to the API which cloudflared will download and use |
I had the similar issue with |
As a temporary fix for anyone reading, deleting the gateway Pod was required to solve this race condition. |
The current cloudflared image in the controller makes HTTPRoutes to not work. After changing the container image to cloudflare/cloudflared:2024.12.2, HTTPRoutes start to work
cloudflare-kubernetes-gateway/config/manager/manager.yaml
Lines 60 to 62 in 2d2113a
With
cloudflared:2024.11.1
:With
cloudflared:2024.12.2
(cloudflare/cloudflared@sha256:cb38f3f30910a7d51545118a179b8516eb7066eac61855d62ce6ed733c54ce70):The text was updated successfully, but these errors were encountered: