aws: Default to AWS CCM v1.36.1 for all k8s versions - #18649
Merged
Merged
Conversation
hakman
approved these changes
Jul 30, 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 |
kubernetes-prow Bot
added a commit
that referenced
this pull request
Jul 30, 2026
…49-origin-release-1.36 Automated cherry pick of #18649: aws: Default to AWS CCM v1.36.1 for all k8s versions
rifelpet
added a commit
to rifelpet/test-infra
that referenced
this pull request
Aug 20, 2026
The AWS CCM route controller races node registration and leaves some nodes without a route, which black-holes pod traffic under kubenet. Upstream cloud-provider-aws fixed this in kubernetes#1388, but no v1.34.x/v1.35.x image carrying the fix was ever released, so kops pinned CCM to v1.36.1 instead in kubernetes/kops#18649. That is on master and release-1.36; release-1.34 and release-1.35 still map to v1.34.0. It is a race rather than a hard failure, so the failing set churns week to week -- roughly 25 of these jobs are red at any moment while the ko36 and latest rows are green. Skip the ko34/ko35 kubenet combinations on AWS until the pin is backported. 48 jobs.
rifelpet
added a commit
to rifelpet/test-infra
that referenced
this pull request
Aug 20, 2026
The AWS CCM route controller races node registration and leaves some nodes without a route, which black-holes pod traffic under kubenet. Upstream cloud-provider-aws fixed this in kubernetes#1388, but no v1.34.x/v1.35.x image carrying the fix was ever released, so kops pinned CCM to v1.36.1 instead in kubernetes/kops#18649. That is on master and release-1.36; release-1.34 and release-1.35 still map to v1.34.0. It is a race rather than a hard failure, so the failing set churns week to week -- roughly 25 of these jobs are red at any moment while the ko36 and latest rows are green. Skip the ko34/ko35 kubenet combinations on AWS until the pin is backported. 48 jobs.
rifelpet
added a commit
to rifelpet/test-infra
that referenced
this pull request
Aug 20, 2026
The AWS CCM route controller races node registration and leaves some nodes without a route, which black-holes pod traffic under kubenet. Upstream cloud-provider-aws fixed this in kubernetes#1388, but no v1.34.x/v1.35.x image carrying the fix was ever released, so kops pinned CCM to v1.36.1 instead in kubernetes/kops#18649. That is on master and release-1.36; release-1.34 and release-1.35 still map to v1.34.0. It is a race rather than a hard failure, so the failing set churns week to week -- roughly 25 of these jobs are red at any moment while the ko36 and latest rows are green. Skip the ko34/ko35 kubenet combinations on AWS until the pin is backported. 48 jobs.
rifelpet
added a commit
to rifelpet/kops
that referenced
this pull request
Sep 10, 2026
Three changes, one per review comment: Say "dropping support for the oldest minor" rather than "dropping the oldest minor", since "dropping" now also reads as release terminology. Applied to the heading and to the reference's summary as well as the flagged line, so the doc stays consistent with itself. Record why the AWS cloud controller manager is no longer keyed on the Kubernetes minor. It was deliberately flattened in kubernetes#18649 because the provider is stable enough that one 1.x build works across every Kubernetes version kOps supports. That is a compatibility judgement, not something forced by the provider's backport policy. Also correct the claim while here: Azure carries a single pin but was never per-minor, so only AWS changed. Make the boundary between the two documents self-evident. Each now opens by saying what it is for and what it deliberately does not cover, so a reader landing on either one can tell immediately whether it is the page they want.
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
2 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.
1.36.1 was published here: kubernetes/k8s.io#9796
AWS CCM has been stable enough that we dont need to use minor-version-specific CCM builds. 1.36.X should be compatible with all of kops' supported k8s versions.
/cc @hakman