feat: replace kube-proxy with cni functionality #105
Conversation
This file contains 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
fitbeard
force-pushed
the
feat/life_after_kube-proxy
branch
from
ee34f96
to
5edc615
Compare
fitbeard
force-pushed
the
feat/life_after_kube-proxy
branch
from
5edc615
to
97b1d1c
Compare
fitbeard
force-pushed
the
feat/life_after_kube-proxy
branch
from
97b1d1c
to
a857598
Compare
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.
Second try to get rid of kube-proxy for EL9 without legacy iptables. All info in a previous PR comments: #48
Also I'm not sure where to put something like this:
cilium_replace_kube_proxy: "{{ kubernetes_remove_kube_proxy }}"