Forwardport 2.5.12 charts #1727
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
added 3 commits
February 9, 2022 23:16
This reverts commit ede5655.
aiyengar2
force-pushed
the
forwardport_25_charts
branch
from
bb082a0 to
e891183
Compare
aiyengar2
force-pushed
the
forwardport_25_charts
branch
from
e891183 to
0b6c2e9
Compare
samkulkarni20
approved these changes
Feb 10, 2022
pennyscissors
approved these changes
Feb 10, 2022
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.
This PR forward ports charts released in Rancher 2.5.12 to the Rancher 2.6 branch.
How does this PR work?
configuration.yamlto validate against the release-v2.5 branch (commit 1)make validate, which will compare the contents of our current directory against the contents of thedev-v2.5branch, copy over assets and charts, modify theindex.yaml, and generate arelease.yamlthat will mark charts that were modified or added if we were to make a release fromdev-v2.6->release-v2.5(commit 2)configuration.yaml(commit 3), delete therelease.yaml(commit 5), and runmake validateagain (commit 6) to generate the release.yaml that marks charts that were modified or added if we were to make a release fromdev-v2.6->release-v2.6. This generates the release.yaml as we expect.commit 4 was a manual change made where I ran
rm -rf charts/rancher-operator charts/rancher-operator-crd assets/rancher-operator assets/rancher-operator-crd && make indexin order to delete the forward ported rancher-operator charts, since we decided we did not want to move forward with forward porting them.