[dev-v2.9] rancher-logging 104.1.3+up4.8.0 update

[jmeza-xyz]

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#46499

Solution

This PR backports the changes from #4907 to dev-2.9 branch.

QA Testing Considerations

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

[mallardduck]

Just one small note to look into. Overall looks correct other than that. But @jbiers is the definitive authority here as this was originally her changes.

Note: One obvious issue is release.yaml but that doesn't matter right now. This can't merge until after current release cycle which will change that anyway. So fixing now will just mean needing to fix again later.

[mallardduck]

Does this tag apply to this version of logging?

In this case the 2.9 chart is still targeting 4.8.0 of upstream charts. Whereas the 2.10 charts is tracking 4.10.0, so we may want to take care when backporting to avoid any changes there that are specific to 2.10's chart.