[release-v2.8] OOB Charts release for rancher-windows-gmsa 3.0.0, rancher-provisioning-capi 100.0.0+up0.0.1 and 103.0.0+up0.0.1, and rancher-cis-benchmark 4.2.0 and 5.0.0

[lucasmlp]

Issues:

rancher-windows-gmsa:

• Copy rancher-windows-gmsa version 102.x.x to 103.0.0 #2864
• Copy rancher-windows-gmsa version 1.x.x to 2.0.0 fix #2893
• Add rancher-windows-gmsa 3.x.x release line corresponding to Rancher 2.8.x #3005

rancher-provisioning-capi:

100.0.0+up0.0.1

• make forward-port provisioning 100.0.0+up0.0.1 #3022

103.0.0+up0.0.1

• [dev-v2.8] Add provisioning capi chart #2953

rancher-cis-benchmark:

4.2.0

• make forward-port rancher-cis 4.2.0 #3018

5.0.0

• copy rancher-cis-benchmark version 102.x.x to 103.x.x #2857
• [v2.7] Add K8s v1.27 support in CIS-Benchmark #2839
• Release 5.0.0-rc1 | Bump security scan to v0.2.13 | Remove 4.2.0-rc1 #2963
• [dev-v2.8] Add CIS 1.24 and 1.7 in dev-v2.8 and bump the chart version #2988
• [dev-v2.8] Update CIS Benchmark version and kube-version #3066
• Unrc cis benchmark 5.0.0 #3163

Charts Checklist (built for v0.5.2 charts-build-scripts)

Checkpoint 0: Validate release.yaml

Validation steps:

• Each chart version in release.yaml DOES NOT modify an already released chart. If so, stop and modify the versions so that it releases a net-new chart.
• Each chart version in 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:

• Running make unzip to regenerate the charts/ from scratch, then git diff to check differences between assets/ and charts/ 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:

• The index.yaml file has an entry for each chart version. (Automated by make validate)
• The index.yaml entries for each chart matches the Chart.yaml for each chart. (Automated by make validate)
• Each chart has ALL required annotations
  • kube-version annotation
  • rancher-version annotation
  • permits-os annotation (indicates Windows and/or Linux)

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.