Upgrade notes for CNI #379
Conversation
kubermatic-bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: youssefazrak The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubermatic-bot
added
approved
|
@irozzo-1A @xrstf PTAL |
|
|
||
| ```bash | ||
| iptables -t nat -D POSTROUTING -s 172.25.0.0/16 ! -d 224.0.0.0/4 -j MASQUERADE | ||
| iptables -t nat -D POSTROUTING ! -s 172.25.0.0/16 -d 172.25.0.0/16 -j MASQUERADE |
There was a problem hiding this comment.
the pod CIDR cannot be configured to be different from 172.25.0.0/16? In such case we should mention that those commands should be adapted accordingly
There was a problem hiding this comment.
From Kubermatic perspective, it is hardcoded for the user clusters.
I agree though it's better to make the point clear. @irozzo-1A updated the sentence accordingly.
|
/lgtm |
|
LGTM label has been added. Git tree hash: 5258812ffe5a23261c72f1f3e00fac1c107d536b
|
When upgrading to Kubermatic v2.12, Flannel version is bumped to v0.11 which has an issue when detecting/flushing the iptables of the nat table/POSTROUTING chain.
This leads to having communication broken when using NetworkPolicies and Pods trying to reach each other on different nodes.
This PR introduces a small note on the upgrade document for 2.11 > 2.12 with a workaround.