fix(rancher-logging): [4.10] add priorityClassName to DS resources

[jmeza-xyz]

Issue:

rancher/rancher#49048 && SURE-9662

Solution

Added priorityClassName to DS resources for k3s/rke/rk2 only if value is populated in values.yaml

      {{- 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

[mallardduck]

Before your first commit here, I think we should increment the package version. Then make charts, then apply the commits that exist here.

So in order:

1. Increment Rancher Logging version - in package.yaml increment the -rancher.{num} part
2. PACKAGE=rancher-logging/4.10 make charts
3. Cherry pick commit 1 from this,
4. PACKAGE=rancher-logging/4.10 make charts

(note cannot cherry pick commit 2 from this as mark charts results are different due to step 1 commit)

[jmeza-xyz]

Before your first commit here, I think we should increment the package version. Then make charts, then apply the commits that exist here.

So in order:

1. Increment Rancher Logging version - in package.yaml increment the `-rancher.{num}` part

2. PACKAGE=rancher-logging/4.10 make charts

3. Cherry pick commit 1 from this,

4. PACKAGE=rancher-logging/4.10 make charts

(note cannot cherry pick commit 2 from this as mark charts results are different due to step 1 commit)

Understood, made the changes in sequence as requested. Please let me know if I need to do anything else. Thanks!

[mallardduck]

Cool - now that this is merged, you can create a new PR (or update the other one) similar what I mentioned here: rancher/charts#5212 (review)

[jmeza-xyz]

Cool - now that this is merged, you can create a new PR (or update the other one) similar what I mentioned here: rancher/charts#5212 (review)

Will do, thanks!