[release-v2.6] OOB Charts release for Monitoring Chart 0.3.0+up0.3.3 #2758
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.
Charts Checklist (built for v0.3.x charts-build-scripts)
Checkpoint 0: Validate
release.yaml
Validation steps:
release.yaml
DOES NOT modify an already released chart. If so, stop and modify the versions so that it releases a net-new chart.release.yaml
IS exactly 1 more patch version than the last released chart version. If not, stop and modify the versions so that it releases a net-new chart.Checkpoint 1: Compare contents of assets/ to charts/
Validation steps:
make unzip
to regenerate thecharts/
from scratch, thengit diff
to check differences betweenassets/
andcharts/
yields NO differences or innocuous differences.IMPORTANT: Do not undo these changes for future steps since we want to keep the charts/ that match the current contents of assets!
Checkpoint 2: Compare assets against index.yaml
Validation steps:
index.yaml
file has an entry for each chart version.index.yaml
entries for each chart matches theChart.yaml
for each chart.Checkpoint 3: Logical Checks
Validation steps (requires manual inspection of differences between previous and latest chart version):
repository
andtag
on the same level to ensure the rancher-images.txt is generated correctly for it for airgap scenarios.