docs: improve guide to setup Cilium overlay on EKS #19207
Merged
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
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
qmonnet
requested changes
Mar 21, 2022
There was a problem hiding this comment.
Thanks a lot for your contribution! Please find some comments below.
Also, please drop the Markdown syntax for your commit description. The # symbols are usually marking comments in git descriptions, and the email address for the Signed-off-by: tag is improperly formatted (see the complaints from checkpatch in the BPF checks).
qmonnet
added
area/documentation
maintainer-s-little-helper
bot
removed
the
dont-merge/needs-release-note-label
qmonnet
requested review from
a team and
christarazi
and removed request for
a team
oliwave
force-pushed
the
docs-patch
branch
2 times, most recently
from
1cf49b8
to
13f5cef
Compare
|
@christarazi Please help me review the PR, thanks! |
christarazi
requested changes
Mar 28, 2022
oliwave
force-pushed
the
docs-patch
branch
4 times, most recently
from
f0c8019
to
9ea5e81
Compare
|
@christarazi I've picked out the chains that will affect routing decisions. And since iptables is not flushed, users don't have to restart |
qmonnet
approved these changes
Apr 11, 2022
christarazi
reviewed
Apr 11, 2022
I've added several documentation steps to properly install Cilium overlay mode on EKS, since removing the `aws-node` daemonSet will not clear the iptables rules and the leftover rules will affect routing and filtering decisions. The issue I'm having is when the source pod is set to `hostNework` mode, the destination pod unable to reply packets through `cilium_vxlan` because of the following AWS CNI residual iptables rules. And also the nodes cannot access pods on different nodes. ``` -A PREROUTING -i eni+ -m comment --comment "AWS, outbound connections" -m state --state NEW -j AWS-CONNMARK-CHAIN-0 -A PREROUTING -m comment --comment "AWS, CONNMARK" -j CONNMARK --restore-mark --nfmask 0x80 --ctmask 0x80 -A POSTROUTING -m comment --comment "AWS SNAT CHAIN" -j AWS-SNAT-CHAIN-0 -A AWS-CONNMARK-CHAIN-0 ! -d 10.2.0.0/16 -m comment --comment "AWS CONNMARK CHAIN, VPC CIDR" -j AWS-CONNMARK-CHAIN-1 -A AWS-CONNMARK-CHAIN-1 -m comment --comment "AWS, CONNMARK" -j CONNMARK --set-xmark 0x80/0x80 -A AWS-SNAT-CHAIN-0 ! -d 10.2.0.0/16 -m comment --comment "AWS SNAT CHAIN" -j AWS-SNAT-CHAIN-1 -A AWS-SNAT-CHAIN-1 ! -o vlan+ -m comment --comment "AWS, SNAT" -m addrtype ! --dst-type LOCAL -j SNAT --to-source 10.2.2.245 --random-fully ``` Signed-off-by: Oliver Wang <a0924100192@gmail.com>
christarazi
added
the
integration/cloud
qmonnet
approved these changes
Apr 12, 2022
qmonnet
added
the
ready-to-merge
I see. Sorry for bothering you. |
|
@oliwave Thanks for your contribution! |
tklauser
added
backport-pending/1.11
backport-done/1.11
tklauser
moved this from Needs backport from master
to Backport done to v1.11
in 1.11.5
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.
I've added several documentation steps to properly install Cilium overlay mode on EKS, since removing the
aws-nodedaemonSet will not clear the following iptables rules and the leftover rules will affect routing and filtering decisions.Signed-off-by: Oliver Wang a0924100192@gmail.com