nodeup: load ip_set module and disable firewalld on RHEL10 - #18478
Merged
k8s-ci-robot merged 1 commit intoJun 18, 2026
Merged
Conversation
Two related fixes for Calico on the ForceNftables() distros (RHEL10+, Rocky10+, etc.). Load the ip_set kernel module alongside nf_tables and nf_conntrack. Calico's Felix unconditionally starts an ipsetsManager that shells out to "ipset list -name" during dataplane resync, even when NFTablesMode is Enabled. On RHEL10-family kernels ip_set is not auto-loaded, so the ipset call returns EINVAL and Felix panics in a tight loop, crashing calico-node and blocking cluster Up on every arm64 grid cell. Disable and mask firewalld via a new disableFirewalld step on FirewallBuilder, gated on Distribution.ForceNftables(). firewalld's default-reject filter_INPUT/filter_FORWARD policies and periodic-reload behavior conflict with the iptables/nftables rules CNIs install for pod and service traffic; Calico's own requirements doc and RKE2 both document that firewalld must be disabled on hosts running these CNIs. The disable/mask sequence is idempotent and a no-op where firewalld is not installed, so this is net-neutral on the cloud images that already strip firewalld (AWS RHEL/Rocky AMIs, Rocky GenericCloud) and net- positive on the GCE-optimized Rocky 10 image where firewalld ships active and breaks Calico BGP keepalives in BPF mode.
rifelpet
force-pushed
the
disable-firewalld-rhel10
branch
from
June 18, 2026 16:11
3af5728 to
6869831
Compare
hakman
approved these changes
Jun 18, 2026
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Member
|
/override pull-kops-e2e-k8s-gce-ipalias |
Contributor
|
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-k8s-gce-ipalias DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
k8s-ci-robot
added a commit
that referenced
this pull request
Jun 18, 2026
…78-origin-release-1.36 Automated cherry pick of #18478: nodeup: load ip_set module and disable firewalld on RHEL10
k8s-ci-robot
added a commit
that referenced
this pull request
Jun 19, 2026
…78-origin-release-1.35 Automated cherry pick of #18478: nodeup: load ip_set module and disable firewalld on RHEL10
This file contains hidden or 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
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.
Summary
Two related fixes for kops nodeup on the
ForceNftables()distros (RHEL 10+, Rocky 10+):ip_setkernel module alongsidenf_tables/nf_conntrackinloadKernelModules.firewalld.servicevia a new step onFirewallBuilder, gated onDistribution.ForceNftables().Together these unblock the failing Calico cells in the
e2e-kops-grid-calico-{rhel10,rocky10}*grid, which produce two distinct failure modes today.Problem
Mode 1 — Felix
ipsetsManagerpanics (arm64 cells)Calico v3.31's Felix unconditionally starts an
ipsetsManagerthat shells out toipset list -nameduring dataplane resync, even whenNFTablesMode: Enabledis in effect. On RHEL 10-family arm64 kernels theip_setmodule isn't auto-loaded, so the netlink request returnsEINVALand Felix panics in a tight loop, taking calico-node with it. Every node reportsCrashLoopBackOff, validation fails after ~25 min, Up returns exit 1.The relevant Felix log on a failing node:
[ERROR] felix/ipsets.go:758: Bad return code from 'ipset list -name'. stderr="ipset v7.11: Kernel error received: Invalid argument"
[PANIC] felix/ipsets.go:416: Failed to update IP sets after multiple retries.
lsmodon the same node confirmsip_setis absent whilenf_tablesandnf_conntrack(already modprobed by kops) are present.Example failing jobs:
Mode 2 — BGP keepalives killed by firewalld interaction (GCE x86_64 cells)
On the GCE-optimized Rocky Linux 10 image,
firewalld.servicestarts at boot:Starting firewalld.service - firewalld - dynamic firewall daemon..., and the resulting nft ruleset contains a populatedtable inet firewalldwith default-rejectfilter_INPUTandfilter_FORWARDpolicies plus act state invalid droprule. firewalld's periodic-reload behavior plus thatct state invalid droprace against Calico's BPF-mode INPUT chain rule:which TCP-RSTs any BGP keepalive that arrives after the session's conntrack entry has been dropped. BIRD then logs
Error: Hold timer expiredon all peers simultaneously and the mesh never recovers. Cluster validation succeeds but e2e tests time out at the 60-minute kubetest2 cap.This pattern persists even with
networking.calico.nftablesMode: Enabledset (the field added in #18452), confirming the flap isn't caused by Felix'snft_compatusage. the host-level firewalld is the remaining disturbance.Example failing builds:
nftablesMode)Why only the GCE image
Empirical comparison from this investigation's own artifacts:
firewalld.servicestarted?table inet firewalldin nft?rocky-linux-cloud/rocky-linux-10-optimized-gcp-v20260526(x86_64)309956199498/RHEL-10.1.0_HVM-...arm64-...(Red Hat AMI)The CIQ-built GCE-optimized spin ships firewalld active; the Red Hat AWS AMIs and the upstream Rocky
GenericCloudqcow2 don't. Disabling firewalld in nodeup is therefore a no-op on the AWS path and a fix on the GCE path.Fix
upup/pkg/fi/nodeup/command.go—loadKernelModules: appendip_setto theForceNftables()modprobe list.modprobealready logs warnings on failure rather than aborting nodeup, so the call is safe on hosts where the module package isn't installed.nodeup/pkg/model/firewall.go— newdisableFirewalld(c)step: mirrors the existingdisableNMCloudSetuppattern. it writes a marker file under/etc/kops/and usesOnChangeExecuteto runsystemctl disable --now firewalld.serviceandsystemctl mask firewalld.service, both wrapped inbash -c '... 2>/dev/null; true'so they're safe no-ops on images where firewalld isn't installed. Gated onb.Distribution.ForceNftables().Precedent for unconditionally disabling firewalld