Override the Default logback.xml with the HiveMQ Platform Operator

The article refers to https://github.com/hivemq/helm-charts/tree/master/charts/hivemq-platform (HiveMQ Platform) version:

NAME                           	CHART VERSION	APP VERSION	DESCRIPTION
hivemq/hivemq-platform         	0.2.18       	4.30.0     	HiveMQ Platform Helm Chart (new)

The article explains how to deliver a customized logback.xml to the HiveMQ Platform containers.

\uD83D\uDCD8 Instructions

Prepare the logback.xml and test it locally first.

Create a ConfigMap from the customized logback.xml:

kubectl create configmap logback-configuration --from-file logback.xml --namespace hivemq

Override the default HiveMQ Logback folder by adding the element to the env array in the hivemq-platform’s values.yaml. The default Logback folder is /opt/hivemq/conf and the following example will override the default value with /opt/hivemq/logback-my-configuration:
```
nodes:
  env:
    - name: HIVEMQ_LOGBACK_CONFIG_FOLDER
      value: /opt/hivemq/logback-my-configuration
```

Add the element to the additionalVolumes array in the hivemq-platform’s values.yaml:

additionalVolumes:
  - type: configMap
    name: logback-configuration
    mountName: logback-configuration
    containerName: hivemq
    path: /opt/hivemq/logback-my-configuration

Execute the helm upgrade command to pick up the changes:

helm upgrade my-broker --install hivemq/hivemq-platform --values hivemq-platform-values.yaml

If everything is correct the rolling restart will happen.

Override the Default logback.xml with the HiveMQ Platform Operator

\uD83D\uDCD8 Instructions

\uD83D\uDCCB Related articles