-
Notifications
You must be signed in to change notification settings - Fork 94
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
xDS: Locality leak on GameServer event handling #585
Labels
kind/bug
Something isn't working
Comments
Interesting, definitely a bug. |
Not sure if related, but just had a weird occurrence where I deleted an allocated ➜ agones-xonotic-xds git:(examples/xonotic-xds) ✗ curl -s http://localhost:9091/config | jq
{
"admin": {
"address": "0.0.0.0:9091"
},
"clusters": {
"default": {
"localities": [
{
"locality": null,
"endpoints": []
},
{
"locality": null,
"endpoints": [
{
"address": "34.127.72.131:7118",
"metadata": {
"quilkin.dev": {
"tokens": []
}
}
}
]
},
{
"locality": null,
"endpoints": [
{
"address": "34.127.72.131:7118",
"metadata": {
"quilkin.dev": {
"tokens": []
}
}
}
]
}
]
}
},
"filters": [
{
"name": "quilkin.filters.capture.v1alpha1.Capture",
"config": {
"metadataKey": "quilkin.dev/capture",
"suffix": {
"size": 3,
"remove": true
}
}
},
{
"name": "quilkin.filters.token_router.v1alpha1.TokenRouter",
"config": null
}
],
"management_servers": [
{
"address": "http://quilkin-manage-agones:80"
}
],
"proxy": null,
"version": "v1alpha1"
} Rather odd. Just noting it for whenever someone digs in here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
I'm pretty sure there's a leak in
localities
whenever a GameServer is added or deleted.To watch this, I ran
kubectl port-forward -n 1662074311 quilkin-proxies-8687b95f58-s89tq 9091
to view the http://localhost:9091/config to see changes.Setup: I have a
quilkin manage agones
xDS control plane, and 1quilkin run
instance connected to it.I created 3
GameServers
, and allocated one of them. The/config
json looked as following:I then allocated a second GameServer, and
/config
became this:I expected a single locality, since everything is a single cluster.
I then deleted one of the allocated
GameServers
, and I got this:Which looks to me like a leak of empty localities?
Also very strange
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Have a look at
/config
on the proxy to see what the current config is.Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: