Fix support for VPC CNI + RHEL9#18264
Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom May 3, 2026
Merged
Conversation
k8s-ci-robot
added
the
do-not-merge/work-in-progress
Contributor
|
Skipping CI for Draft Pull Request. |
k8s-ci-robot
added
size/L
Member
Author
|
/test pull-kops-aws-distro-rhel9 |
rifelpet
changed the title
k8s-ci-robot
added
size/M
RHEL 9 ships NetworkManager-cloud-setup, whose nm-cloud-setup.service +
.timer poll IMDS for the secondary IPs assigned to ENIs (the AWS VPC
CNI's pod IPs) and tell NetworkManager to install per-IP source-routing
rules in reserved tables 30200/30201/30400/30401:
30200: from <pod-ip> lookup 30200 proto static
30400: from <pod-ip> lookup 30400 proto static
...
32765: from <secondary-eni-primary-ip> lookup 2 ← AWS VPC CNI
The 30xxx priorities are below the AWS VPC CNI's rule at 32765, so they
take precedence. Pod traffic gets routed through tables that don't have
the routes the CNI needs for the service CIDR or IMDS, and pods can't
reach 100.64.0.1 or 169.254.169.254. Cluster validation times out with
all ebs-csi-node and CoreDNS pods stuck not-ready.
AWS's own VPC CNI troubleshooting guide explicitly calls out that
nm-cloud-setup must be disabled on EC2 nodes using the VPC CNI; EKS
AMIs ship without it, RHEL 9's stock cloud image enables it.
Mask both nm-cloud-setup.service and nm-cloud-setup.timer so neither
the periodic timer nor a package preset can re-enable them, then bounce
the active NetworkManager connections with `
nmcli connection down/up`
to drop the rules and routes nm-cloud-setup pushed before nodeup ran.
A marker file at /etc/kops/nm-cloud-setup-disabled keeps the disable
idempotent across nodeup re-runs.
hakman
approved these changes
May 3, 2026
k8s-ci-robot
added
the
lgtm
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 |
k8s-ci-robot
added
the
approved
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
3 participants
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.
Similar to #18261 but for RHEL 9.
According to RH docs, RHEL9 will have standard support for the foreseeable future.
This presubmit job passed with a temporary override to use VPC CNI + RHEL9 with this fix