[release-v2.8] Feature Charts batch release for epinio, longhorn and neuvector

[lucasmlp]

Issues:

epinio:

• Copy Epinio version from 102.0.3+up1.8.1 to 103.0.0+up1.8.1 #2841

102.0.4+up1.9.0

• make forward-port epinio 102.0.4+up1.9.0 #3013

103.0.0+up1.8.1 and 103.0.1+up1.9.0:

• Epinio 2.8 branching #2980

103.0.2+up1.10.0

• Epinio bump to 1.10.0 #3064

longhorn:

• Copy longhorn version 102. x.x to 103.0.0 #2854

103.0.0+up1.3.3, 103.1.0+up1.4.3 and 103.2.0+up1.5.1

• Longhorn charts branching for Rancher v2.8 #3072

neuvector:

• Copy neuvector version 102. x.x to 103.0.0 #2855
• Copy neuvector-monitor version 102. x.x to 103.0.0 #2859

102.0.4+up2.6.2

• Forward-port charts neuvector, neuvector-crd and neuvector-monitoring 102.0.4+up2.6.2 #2951

102.0.5+up2.6.4

• Forward port NeuVector v2.6.4 after OOB release #3153
• Forward port NeuVector Monitor v2.6.4 after OOB release #3154

103.0.0+up2.6.2

• Add NeuVector chart version 2.6.2  #3027
• NeuVector monitor chart 2.6.2 v2.8 #3028

103.0.0+up2.6.4

• Add NeuVector chart version 2.6.4 #3159
• Add NeuVector Monitor chart version 2.6.4 #3160

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:

• 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.