Bump kubernetes to v1.30.2 #668
Merged
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
|
Hi @Iceber, DetailsInstructions for interacting with me using comments are available here. |
Signed-off-by: Iceber Gu <[email protected]>
Signed-off-by: Iceber Gu <[email protected]>
Signed-off-by: Iceber Gu <[email protected]>
Signed-off-by: Iceber Gu <[email protected]>
Signed-off-by: Iceber Gu <[email protected]>
|
fix #665 |
Iceber
force-pushed
the
bump_kubernetes
branch
3 times, most recently
from
586da1c
to
68f6d15
Compare
…to false Signed-off-by: Iceber Gu <[email protected]>
Signed-off-by: Iceber Gu <[email protected]>
|
Issues to be fixed:
|
This was referenced Jun 14, 2024
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.
What type of PR is this?
/kind feature
New Support Kubernetes Resources:
storagemigration.k8s.ioWhat this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: