Customizing logging-operator-logging application deployment (fluentBit, fluentD)

Problem
Customizing Logging-operator-logging's component is not possible through the usual Kommander's --installer-config yaml file. For cases where components of the logging-operator-logging needs to be customized, like FluentD's resource limit or number of replicas. Please see the following examples.

Solution
Create a configMap named logging-operator-logging-overrides, that contains the desired customized values.

For example, fluentd's resource request/limit:

apiVersion: v1
kind: ConfigMap
metadata:
  name: logging-operator-logging-overrides
  namespace: kommander
data:
  values.yaml: |
    fluentd:
      resources:
        limits:
          cpu: 1
          memory: 2000Mi
        requests:
          cpu: 1
          memory: 1500Mi

or replicas:

data:
  values.yaml: |
    fluentd:
      replicas: 3

This would be picked up by the logging-operator and would restart fluentd with the new configuration.

You can also describe the default logging-operator-logging's configMap to see other configurations applied to fluentd and fluentbit.