You may notice that if you are trying to make Helm value changes to the "logging-operator" Kommander platform app via the web UI, that those changes are not being applied.
Solution
This is due to an issue related to how the logging-operator pods are organized.
When you make configuration changes to the logging-operator app via the Kommander UI, a configmap is generated called "logging-operator-config-overrides".
Configs related to the "logging-operator-logging-fluentbit" and "logging-operator-logging-fluentd" pods need to be in a configmap called "logging-operator-logging-overrides".
To create this based on changes you made in the UI, you can download the existing configmap, change the name, then re-apply it. To download it:
kubectl get configmap -n kommander logging-operator-config-overrides -o yaml > logging-operator-config-overrides.yaml
Make edits to this file to change the "metadata.name" field, then change the name of the file to logging-operator-logging-overrides.yaml. Here is an example of what it might look like:
apiVersion: v1
data:
values.yaml: |-
fluentd:
resources:
limits:
memory: 500Mi
fluentbit:
resources:
limits:
memory: 900Mi
kind: ConfigMap
metadata:
labels:
kommander.d2iq.io/managed-by-kind: AppDeployment
name: logging-operator-logging-overrides
namespace: kommander
You can then apply the new file with:
kubectl apply -f logging-operator-logging-overrides.yaml