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
helm: Disable BPF masquerading in v1.10+ #17824
helm: Disable BPF masquerading in v1.10+ #17824
Conversation
c656d01
to
b70e353
Compare
/test |
In Cilium v1.10, we disabled kube-proxy-replacement by default but left BPF masquerading enabled. Since the latter requires the former, the default installation results in a warning. This commit fixes the warning by disabling BPF masquerading as well on new v1.10+ deployments. Fixes: 5412142 ("install: Disable kube-proxy-replacement by default") Signed-off-by: Paul Chaignon <paul@cilium.io>
b70e353
to
3ef072c
Compare
The new push only adds a comment. The tests were previously all green with the exception of k8s-1.21-kernel-4.19 which was failing with known flake #17353. Marking ready to merge. |
@pchaigno FYI 1.10 docs mention |
@stevo-f3 Nice catch! Do you want to send a pull request to fix it? We can then backport the fix to all stable branches. |
In Cilium v1.10, we disabled kube-proxy-replacement by default but left BPF masquerading enabled. Since the latter requires the former, the default installation results in a warning.
This pull request fixes the warning by disabling BPF masquerading as well on new v1.10+ deployments.
Fixes: #15422.