Add check to validating admission webhook to reject EnvoyConfigs that manage an already existent node-id #160
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
size/M
Requires about a day to complete the PR or the issue.
Add a check in the validating admission webhook for EnvoyConfig resources to avoid a new EnvoyConfig to be created for a node-id that is already being managed by an existent EnvoyConfig. This situation causes the discovery service to enter an infinite reconciliation loop as the EnvoyConfigRevisions match 2 (or more) different EnvoyConfigs.
This could also be fixed by forcing the node-id to be the same as the EnvoyConfig resource name, but this could break existing configurations.
The text was updated successfully, but these errors were encountered: