[dev-v2.11] rancher-logging 106.0.0-rc.1+up4.10.0-rancher.2 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)

---

Issue:

rancher/rancher#49048 && SURE-9662

Solution

Added priorityClassName to DS resources for k3s/rke/rk2 only if value is populated in values.yaml. We should also backport this to rancher-logging 105 on dev-v2.10 branch.

      {{- with .Values.priorityClassName }}
      priorityClassName: {{ . }}
      {{- end }}

Added podPriorityClassName in Logging/FluentBitAgent generic templates with the option to set it in the global or fluentd/fluentbit keys.

    {{- with (default .Values.priorityClassName .Values.fluentd.podPriorityClassName) }}
    podPriorityClassName: {{ . }}
    {{- end }}

    {{- with (default .Values.priorityClassName .Values.fluentd.podPriorityClassName) }}
    podPriorityClassName: {{ . }}
    {{- end }}

# values.yaml addition

fluentbit:
  podPriorityClassName: ""
fluentd:
  podPriorityClassName: ""

QA Testing Considerations

Example values.yaml used for testing. Comment out the podPriorityClassName to test priorityClassName: global-level-test is passed down to all resources.

additionalLoggingSources:
  rke2:
    enabled: true
debug: true
fluentbit:
  podPriorityClassName: resource-level-test
  resources:
    limits:
      memory: 512Mi
    requests:
      cpu: 20m
      memory: 512Mi
fluentd:
  replicas: 1
  podPriorityClassName: resource-level-test
  resources:
    limits:
      memory: 512Mi
    requests:
      cpu: 20m
      memory: 512Mi
priorityClassName: global-level-test
global:
  seLinux:
    enabled: true

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

This PR is not correct - first the PR in ob-team-charts should be corrected for feedback, then merged.
After that, this repo should only need to be updated to:

1. In package.yaml update the upstream chart version to use the new ob-team-charts version for this chart.
2. Also increment the "rancher/charts local" RC version,
3. Do the normal make {prepare,patch,charts} steps.

So the end result will be a version that looks something like: 106.0.0-rc.2+up4.10.0-rancher.2

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

[jmeza-xyz]

This PR is not correct - first the PR in ob-team-charts should be corrected for feedback, then merged. After that, this repo should only need to be updated to:

1. In `package.yaml` update the upstream chart version to use the new `ob-team-charts` version for this chart.

2. Also increment the "rancher/charts local" RC version,

3. Do the normal make {prepare,patch,charts} steps.

So the end result will be a version that looks something like: 106.0.0-rc.2+up4.10.0-rancher.2

Hi @mallardduck I've made the updates you requested. Please let me know if I did anything wrong. Thanks and apologies for the delay!

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