[dev-v2.11] rancher-backup 106.0.0+up7.0.0-alpha.3 update

[apoorvajagtap]

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: rancher/rancher#48832

Additional detail:

bumps k8s and rancher supported version for rancher-backup.

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

[mallardduck]

Hey @apoorvajagtap - this looks very good, however it's best to do this change at https://github.com/rancher/backup-restore-operator directly and then release an RC. This is because we fully control/produce the project so doing it there will prevent us needing any patch here.

I believe that @alexandreLamarre just made a similar release and PR - so you can review that and make changes in a similar way in the BRO repo. https://github.com/rancher/backup-restore-operator/blob/337159ca1f7d40fadf264336f4fbbef10334ddcf/charts/rancher-backup/Chart.yaml#L10

Once you make a PR there and we merge it we can create another non-stable tag (alpha/rc), then the PR would look similar to: #5107