Fix root loggingref

[skanakal]

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:

rancher/rancher#49057

Solution

allow root logging to inherit loggingRef from values.yaml, ensuring it behaves like other logging sources...

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.

[w13915984028]

Please also take a look the fluentbitagent.yaml under kube-audit, from my test, without a loggingRef, the kube-audit log is also sent to root-fluend, thanks.

Harvester patches the pulled rancher-logging chart locally.

https://github.com/harvester/harvester-installer/pull/980/files#diff-262d20f5e1057034255c9c16590b8a3e94f4e059297f837c1b8d31f406f1ede0

[skanakal]

@w13915984028 You can set this thru below, and that's being set here: https://github.com/rancher/charts/blob/dev-v2.11/charts/rancher-logging/106.0.0-rc.1%2Bup4.10.0/templates/loggings/kube-audit/fluentbitagent.yaml#L2-L6

with the helper function https://github.com/rancher/charts/blob/dev-v2.11/charts/rancher-logging/106.0.0-rc.1%2Bup4.10.0/templates/_helpers.tpl#L220

additionalLoggingSources:
  kube-audit:
    enabled: true
    loggingRef: kubeauditlogging
    fluentbit:
      loggingRef: kubeauditlogging

[w13915984028]

@skanakal That's great, thanks.

[mallardduck]

Hiya - if I understand, this helps fix a bug in logging that harvester team observed, but could affect other use cases. Is that correct? If so, can we instead have a PR to apply it to this charts package here: https://github.com/rancher/ob-team-charts/tree/main/packages/rancher-logging/4.10

Note: ob-team-charts is essentially a repo setup the same way rancher-charts is however it's the new source area for O&B team to maintain the rancher specific changes/fixes to Monitoring and Logging charts. Then our team will sync charts from this repo into rancher/charts.