install: Disable BPF masquerading by default #609
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In commit bf2c1f9, we switched
kube-proxy-replacement
to disabled by default. We didn't change the default setting for BPF masquerading, even though it requireskube-proxy-replacement
to be enabled. As a result, default installation result in a warning when BPF masquerading is forcefully disabled.This pull request disables BPF masquerading by default to fix it. We could enable BPF masquerading when
kube-proxy-replacement
is enabled by the user, but it seems more confusing than anything.Fixes: #136.