-
Notifications
You must be signed in to change notification settings - Fork 360
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
bug: race condition? when using mergeGateway and multiple gateways #2968
Labels
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
this is still the issue with 1.0.1. |
this has maybe something to do with infrastructure annotations in gateway. I am trying to reproduce this now with latest main |
-> nothing will work. It is removing original listener and adding foobar listener I went through the configuration and imo it looks quite same |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I have following installation
full yaml spec: https://gist.github.com/zetaab/8caa34f5072d5a8efc5c2425c331c561
and httproutes https://gist.github.com/zetaab/149545f3e0ae17c0b925bafd3512d1eb
When I am adding httproutes and envoy proxies are restarting, it will randomly all services unavailable. When envoy pods are starting I can see following in logs
This means that all services are running (also services that are coming from other gateways than https). However, when the log says
Nothing will work.
Why listeners are loaded in different order sometimes?
Repro steps:
Environment:
eg 1.0.0
Logs:
took listener configurations using egctl
egctl config envoy-proxy listener -n envoy-gateway-system -l gateway.envoyproxy.io/owning-gatewayclass=eg-internal
not working:
https://gist.github.com/zetaab/2e0f2f00174d4b6189290e095ebe5cf5
working:
https://gist.github.com/zetaab/08d2f7b3bfbd04a28be14bd990552214
like can be seen: sometimes its missing 400+ rows of configurations. When this happens, I need to delete all other gateways than primary one (located in envoy-gateway-system) and then add other gateways back. Then everything starts to work again.
The text was updated successfully, but these errors were encountered: