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
Rename hostFirewall
and mark stable
#17221
Conversation
8848312
to
414094b
Compare
To plan for future additions to the set of host firewall options, it's better to have hostFirewall be a map rather than a boolean. We should do this now before the host firewall is stable, even if we don't yet have a use case for it. Signed-off-by: Paul Chaignon <paul@cilium.io>
The remaining issues with the host firewall and kube-proxy are resolved. The race condition on node labels was also addressed and the host firewall's status is now present in cilium status. We can now mark the host firewall stable regardless of KPR status. Signed-off-by: Paul Chaignon <paul@cilium.io>
414094b
to
d9ddba4
Compare
test-me-please |
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.
Looks good to me 👍
The changes covered by @cilium/policy are minor (related to the Helm value change in the docs & tests), so I think it's okay to not wait for those reviews. All tests are passing so marking this ready to merge. |
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.
🚀
See commits for details.