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: add 'endpointRoutes.enabled=true' to aws-cni #16045
docs: add 'endpointRoutes.enabled=true' to aws-cni #16045
Conversation
This comment has been minimized.
This comment has been minimized.
This is meant as a temporary workaround for #16007. Signed-off-by: Bruno Miguel Custódio <brunomcustodio@gmail.com>
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.
Do we also want to backport to v1.8?
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.
I'm a little bit nervous that maybe we used to always automatically configure this for chaining mode and somehow we accidentally changed something so that it's not automatic any more (and also implicitly this could mean that for other chaining plugins it's still a problem), but at the same time this seems like an easy workaround for now.
👍
If we think this is also a problem on v1.8.x, we should backport it there too so we can point to the docs and make sure folks are configuring this option. |
I spoke too soon. The PR that introduced this regression for chaining mode (i.e., #15228) wasn't backported to v1.8 so we don't need to backport there either. |
This is meant as a temporary workaround for #16007.