-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: allow disabling pod locality in xDS #10404
Conversation
this means destination rules won't work correctly; but things like VMs and other WorkloadEntries based workloads will. This is not documented as it is meant as a temporary hotfix, with a durable fix for supporting WorkloadEntries coming later.
Issues linked to changelog: |
Visit the preview URL for this PR (updated for commit b9d49b2): https://gloo-edge--pr10404-yuval-k-disable-loca-whog6nen.web.app (expires Tue, 03 Dec 2024 00:27:21 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 77c2b86e287749579b7ff9cadb81e099042ef677 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this and it allows connections from xDS clients that don't have a pod when the env var is set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non blocking comment, will approve otherwise!
When this is enabled - it means destination rules won't work correctly; but things like VMs and other WorkloadEntries based workloads will. This is not documented as it is meant as a temporary hotfix, with a durable fix for supporting WorkloadEntries coming later.
to enable, set DISABLE_POD_LOCALITY_XDS to true in the gloo deployment.
BOT NOTES:
resolves https://github.com/solo-io/solo-projects/issues/7302