-
Notifications
You must be signed in to change notification settings - Fork 335
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 generators should require resource names #2538
Comments
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. |
|
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
Seems like all builders in pkg/xds/envoy requires names now. Closing |
Summary
The xDS generators do not require xDS resources to be named, and there's no checking for that until you get to the consistency snapshot.
Code that looks like it should do nothing will generate anonymous resources, e.g:
There are cases where its OK to generate xDS resources that don't have names, but maybe it's more robust to always require them.
Discuss :)
The text was updated successfully, but these errors were encountered: