-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.32-rc1 #837
Closed
Closed
v1.32-rc1 #837
Conversation
This file contains 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
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
November 28, 2024 17:14
e11d2e8
to
6b1b1f9
Compare
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
December 2, 2024 08:41
6b1b1f9
to
41e532d
Compare
louiseschmidtgen
approved these changes
Dec 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Ben for making the adjustments for the WatchList feature!
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
December 5, 2024 08:10
8eb34ef
to
387d5fe
Compare
bschimke95
changed the base branch from
main
to
KU-2012/disable-breaking-k8s-feature
December 5, 2024 08:11
Note: this PR now only contains the actual version bump. The fixes for 1.32 are done in #869 This PR will be closed after the release. |
bschimke95
force-pushed
the
KU-2012/disable-breaking-k8s-feature
branch
from
December 6, 2024 08:34
31b895e
to
8ac2740
Compare
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
December 6, 2024 08:35
b3ca349
to
edab9ca
Compare
bschimke95
force-pushed
the
KU-2012/disable-breaking-k8s-feature
branch
from
December 6, 2024 09:14
8ac2740
to
938a117
Compare
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
December 6, 2024 09:15
edab9ca
to
4c23fad
Compare
bschimke95
force-pushed
the
KU-2012/disable-breaking-k8s-feature
branch
from
December 6, 2024 13:58
938a117
to
77f7132
Compare
bschimke95
force-pushed
the
KU-2012/test-1.32-rc
branch
from
December 6, 2024 13:59
4c23fad
to
d10634c
Compare
Closing in favour of #877 |
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
Enable and fix 1.32-rc release
Rationale
Upstream Kubernetes 1.32 will be released next week. This PR tests if the current snap is compatible with the current release candidate.
Some changes in the snap are required:
k8s-dqlite
and the consistent read from cache. By default, this feature is enabled on 1.32.For now, we'll disable this feature and do a follow-up investigation what it takes to support that feature in k8s-dqlite.
k8s.io
library versions