-
Notifications
You must be signed in to change notification settings - Fork 3k
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
docs: Clarify use of the eni.subnetTagsFilter option
#19276
Conversation
The `eni.subnetTagsFilter` option is notoriously hard to use correctly. If it is used with tags that don't match the subnet of the pre-attached ENI, Cilium agent will never become ready (cilium#18239). This PR removes it from the ENI documentation (which most users will use as a reference configuration) such that no one enables this option without being aware of its requirements. This PR also adds additional context the Helm value. We might deprecate and remove the option in the future as well (cilium#19181). Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
0ac299f
to
d2bf3c2
Compare
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.
🚢
|
Thanks for the heads up. I'll do a manual backport, thanks.
|
|
Oh, I confused some PRs here. Looking at the current v1.9 branch, yeah I agree that the backport is not needed. Sorry for the noise 🙇♂️ |
The
eni.subnetTagsFilteroption is notoriously hard to use correctly.If it is used with tags that don't match the subnet of the pre-attached
ENI, Cilium agent will never become ready (#18239).
This PR removes it from the ENI documentation (which most users will use
as a reference configuration) such that no one enables this option
without being aware of its requirements. This PR also adds additional
context the Helm value. We might deprecate and remove the option in the
future as well (#19181).
Signed-off-by: Sebastian Wicki sebastian@isovalent.com