Upgrade vsphere charts for k8s 1.27 support #2956
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
jiaqiluo
approved these changes
Sep 7, 2023
snasovich
approved these changes
Sep 8, 2023
lucasmlp
pushed a commit
that referenced
this pull request
Oct 24, 2023
This was referenced Jan 19, 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.
Issue:
rancher/rancher#41792
rancher/rancher#41793
Problem
Update vSphere csi/cpi charts for 1.27 support
Supercharts contain new images that support k8s 1.27 and new functionality/bug fixes pulled in by those images. Chart versions are bumped for Rancher 2.8 clusters.
Solution
Testing
Engineering Testing
Manual Testing
Compared vsphere charts k8s app version and appVersion with upstream, making sure patches are aligned with upstream.
make validatepassed. Charts tested on k8s 1.26+.Automated Testing
QA Testing Considerations
Regressions Considerations
Backporting considerations