[v2.9] pin rancher capi chart version #45438
Open
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:
#45099
Problem
capi chart was being auto upgraded to newer version and if there are some breaking changes in the new CAPI chart it was breaking an older running rancher instance.
Solution
pin CAPI chart to a fix version in rancher through settings.
Testing
rancher docker install and checking the CAPI chart version.
--> successful chart version is same as the one specified in build.yaml
103.2.0+up0.0.1
rancher docker install with env variable to override the chart version to
103.0.0+up0.0.1
--> successful chart version is same as the env variable passed.
Engineering Testing
Manual Testing
Automated Testing
Summary: TODO
QA Testing Considerations
Regressions Considerations
TODO
Existing / newly added automated tests that provide evidence there are no regressions: