Bump to k8s 1.29. #467
Merged
Bump to k8s 1.29. #467
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
The encryption getter now wants an APIServerID, but this field is currently used only for metrics, so we can pass an empty string.
ericpromislow
force-pushed
the
44097-bump-k8s-to-1-29-3
branch
2 times, most recently
from
a289d4e to
b10dff2
Compare
ericpromislow
force-pushed
the
44097-bump-k8s-to-1-29-3
branch
from
b10dff2 to
8f12f25
Compare
mallardduck
approved these changes
May 13, 2024
| github.com/rancher/wrangler v1.0.2 | ||
| github.com/rancher/wrangler/v2 v2.1.4 | ||
| github.com/rancher/lasso v0.0.0-20240424194130-d87ec407d941 | ||
| github.com/rancher/wrangler v1.1.2 |
There was a problem hiding this comment.
Noticed wrangler was downgraded from v2 to v1? Is there a particular reason why there? Seems odd for 1.29 k8s support
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.
The encryption getter now wants an APIServerID, but this field is currently used only for metrics, so we can pass an empty string.