-
Notifications
You must be signed in to change notification settings - Fork 716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-v2.7] Chart Release for Rancher v2.7.12 #3686
Closed
Closed
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
[dev-v2.7] Add EKS 1.2.0 in CIS Benchmark
…ssion [v2.7] fix cis operator permission
[v2.7] bump security scan
[v2.7] Update cis benchmark chart version to v4.4.0-rc1
Bump fleet 0.8.2 rc.3 Starting Cherry Pick for Fleet on release 2.7.12
Co-authored-by: fleet-bot <fleet@suse.de>
Co-authored-by: fleet-bot <fleet@suse.de>
Co-authored-by: fleet-bot <fleet@suse.de>
Starting cherry-pick for 2.7.12 release
Starting cherry-pick for 2.7.12
Starting cherry-pick for 2.7.12
Validation steps
Ex:- longhorn-controller: repository: rancher/hardened-sriov-cni tag: v2.6.3-build20230913
|
nicholasSUSE
changed the title
[release-v2.7] Batch Charts release for 2.7.12 - longhorn; harvester-csi-driver; harvester-cloud-provider; rancher-gke-operator; rancher-aks-operator; rancher-eks-operator; fleet; rancher-cis-benchmark
[release-v2.7] Batch Charts release for 2.7.12 - harvester-csi-driver; harvester-cloud-provider; rancher-gke-operator; rancher-aks-operator; rancher-eks-operator; fleet; rancher-cis-benchmark
Mar 26, 2024
nicholasSUSE
force-pushed
the
1st-batch-release-2.7.12
branch
from
March 26, 2024 18:49
e2518d7
to
d429fd2
Compare
Validation steps
Ex:- longhorn-controller: repository: rancher/hardened-sriov-cni tag: v2.6.3-build20230913
|
lucasmlp
changed the title
[release-v2.7] Batch Charts release for 2.7.12 - harvester-csi-driver; harvester-cloud-provider; rancher-gke-operator; rancher-aks-operator; rancher-eks-operator; fleet; rancher-cis-benchmark
[release-v2.7] Chart Release for Rancher v2.7.12
Mar 26, 2024
Validation steps
Ex:- longhorn-controller: repository: rancher/hardened-sriov-cni tag: v2.6.3-build20230913
|
nicholasSUSE
force-pushed
the
1st-batch-release-2.7.12
branch
from
March 27, 2024 15:42
84fac4f
to
90f52cd
Compare
Validation steps
Ex:- longhorn-controller: repository: rancher/hardened-sriov-cni tag: v2.6.3-build20230913
|
This failed, we are doing 2 separate others |
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.
Charts
rancher-gke-operator
102.1.0+up1.1.7
rancher-eks-operator
102.2.0+up1.2.3
rancher-aks-operator
102.4.0+up1.1.4
fleet
102.2.3+up0.8.3
rancher-cis-benchmark
4.4.0
Longhorn was already release in an out of band release, there is a final commit adding some changes here for sync purposes.
Charts Checklist (built for v0.5.2 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: