Feat/update scs2 1 33 11#267
Merged
Merged
Conversation
This is the files that we only need to have once, across k8s minor versions. Signed-off-by: Kurt Garloff <kurt@garloff.de>
Signed-off-by: Kurt Garloff <kurt@garloff.de>
k8s: v1.33.11 (up from 1.33.10) occm: v2.33.1 (unchanged) csi-cinder: v2.33.1 (unchanged) cni-cilium: v1.18.10 (up from 1.18.9) Signed-off-by: Kurt Garloff <kurt@garloff.de>
schneidarno
approved these changes
May 28, 2026
Contributor
schneidarno
left a comment
There was a problem hiding this comment.
created 1.33.11 cluster on local infrastructure - worked
Member
Author
|
Thanks for testing @schneidarno - you were faster than I was! |
Member
Author
|
Published as |
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.
This commit contains the changes to bring the branch
maint/scs2-1-33up to k8s-v1.33.11.Explanation of the intended use of branches in PR #266.
Once merged, I would create the release on our registry.
Pushed this one for testing as
v0-git.d0560f9