-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set iptables backend to NFT for Canal and Calico VXLAN on Flatcar clusters #2301
Conversation
…sters Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Skipping CI for Draft Pull Request. |
/retest |
/lgtm |
LGTM label has been added. Git tree hash: 14cb46982cce48c5032a6e31dbd10888284c91b0
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: moadqassem 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 |
What this PR does / why we need it:
It happens that after upgrading Canal/Calico to a newer minor version, the pod network connectivity stops working for some reason. This mostly happens on Flatcar-based clusters and not always, but from time to time. This is a known upstream Calico issue and it's being tracked here: projectcalico/calico#5760
As mentioned in projectcalico/calico#5760 (comment), the solution is to set
FELIX_IPTABLESBACKEND
toNFT
.If there's a Flatcar control plane node in the cluster, KubeOne will set
FELIX_IPTABLESBACKEND
toNFT
. Otherwise, KubeOne will setFELIX_IPTABLESBACKEND
toAuto
, which is the current default value and results in Calico automatically determining the iptables backend.This can be overridden by setting the
iptablesBackend
parameter on Canal or Calico VXLAN addon. For example:This might also affect RHEL, but from our testing, it's much less frequent than for Flatcar. To reduce the scope of changes before the release, we'll revisit this after releasing KubeOne 1.5.
What type of PR is this?
/kind bug
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: