Replies: 1 comment 1 reply
-
|
Normally the SUBMARINER-POSTROUTING chain has two set of rules. Sample output: In the above output entry number 1 supports the first use-case and the remaining entries support the second use-case. Looking at the output you shared, I see that you are using Calico CNI. In case of Calico, some of the submariner chains may not be hit as we program Calico IPPools. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The SUBMARINER-POSTROUTING chain is added to the NAT table on non-gateway nodes. I do not understand that cross-cluster traffic between nodes in a cluster is established through vx-submariner, and NAT is not performed. What problem is the SUBMARINER-POSTROUTING chain added to the nat table to solve?
Chain POSTROUTING (policy ACCEPT 219 packets, 13342 bytes)
pkts bytes target prot opt in out source destination
1558K 95M cali-POSTROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 /* cali:O3lYWMrLQYEMJtB5 /
1558K 95M SUBMARINER-POSTROUTING all -- * * 0.0.0.0/0 0.0.0.0/0
1558K 95M KUBE-POSTROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 / kubernetes postrouting rules */
0 0 MASQUERADE all -- * !docker0 172.17.0.0/16 0.0.0.0/0
Beta Was this translation helpful? Give feedback.
All reactions