Skip to content

Fix cri-tools fallback when version lags behind Kubernetes releases - #7

Merged
mweibel merged 1 commit into
mainfrom
fix/cri-tools-fallback
Sep 1, 2026
Merged

Fix cri-tools fallback when version lags behind Kubernetes releases#7
mweibel merged 1 commit into
mainfrom
fix/cri-tools-fallback

Conversation

@mweibel

@mweibel mweibel commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

When a new Kubernetes minor version is released before the matching cri-tools version, the release-set script would fail with an assertion error. Instead of failing, fall back to the latest available cri-tools version and emit a warning.

This allows test matrices to automatically discover new Kubernetes releases without requiring manual version pinning.

Related: cloudscale-ch/cloudscale-cloud-controller-manager#60

When a new Kubernetes minor version is released before the matching
cri-tools version, the release-set script would fail with an assertion
error. Instead of failing, fall back to the latest available cri-tools
version and emit a warning.

This allows test matrices to automatically discover new Kubernetes
releases without requiring manual version pinning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant