[dev-v2.10] rancher-logging 105.2.1-rc.1+up4.10.0 update #5115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checkpoints for Chart Bumps
release.yaml
:Chart.yaml and index.yaml
:index.yaml
file has an entry for your new chart version.index.yaml
entries for each chart matches theChart.yaml
for each chart.Fill the following only if required by your manager.
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.
QA Testing Considerations
Example values.yaml used for testing. Comment out the
podPriorityClassName
to testpriorityClassName: global-level-test
is passed down to all resources.