Enable host firewall in kube-proxy-free CI #11795
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
retest-net-next |
34 tasks
Signed-off-by: Paul Chaignon <paul@cilium.io>
This commit enables the enforcement of host policies in the datapath for our kube-proxy-free CI builds. Since no host policies are loaded, it defaults to allow all on ingress and egress. Signed-off-by: Paul Chaignon <paul@cilium.io>
2fe2b79 to
6da0fe3
Compare
6da0fe3 to
4bd0540
Compare
|
test-me-please |
joestringer
requested changes
Jun 3, 2020
christarazi
approved these changes
Jun 4, 2020
joestringer
approved these changes
Jun 4, 2020
brb
approved these changes
Jun 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This first commit adds a new Helm option to enable the host firewall, which then allows the second commit to enable it in our kube-proxy-free CI builds (K8s 1.11 Linux net-next). The third and last commits fix two issues found this way: (1) a missing case for ARP resolution on
from-{netdev,host}paths, and (2) packet drops when tunneling is enabled. I'm not sure how I missed the second before since I had already ran the CI build (although not with the Helm option).Enabling host firewall on 4.19 is currently blocked by #10567.
Updates: #11799
Fixes: #11507