[dev-v2.10] Add chart for Supportability Review Operator

[masap]

Pull Requests Rules

• Never remove an already released chart!

  • This does not apply to RC's because they are not released.

• Each Pull Request should only modify one chart with its dependencies.

• Pull request title:

  [dev-v2.X] <chart> <version> <action>
  

  • <action>: 1 of (bump; remove; UnRC)

---

Checkpoints for Chart Bumps

release.yaml:

• 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 or minor version than the last released chart version. If not, stop and modify the versions so that it releases a net-new chart.

Chart.yaml and index.yaml:

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

---

Fill the following only if required by your manager.

Issue:

We would like to add our Supportability Review Operator into official Rancher Chart.

Solution

Add chart for Supportability Review Operator.

QA Testing Considerations

cc: @aemneina, @ajithijk

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

[recena]

⚠️ This new addition must update the CODEOWNER /cc @rancher/release-team

[masap]

@recena

This new addition must update the CODEOWNER

Thank you for comment. Is there anything I should do about this?

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

[masap]

Rebased.

[masap]

Resubmitted for dev-v2.11 by #5658.