/
Overriding the logback.xml file in HiveMQ Operator
Overriding the logback.xml file in HiveMQ Operator
This article explains step-by-step how to override the "logback.xml" file in the HiveMQ Operator using ConfigMaps.
A ConfigMap is a Kubernetes API object that lets you store and share non-sensitive, unencrypted configuration information. ConfigMaps allow you to decouple your configurations from your Pods and components, which helps keep your workloads portable
Instructions
Put the
logback.xml
file into a configMap and then mount it to the path/opt/hivemq/conf
in the HiveMQ pod.kubectl create configmap hivemq-logback --from-file=/path/to/logback.xml -n <broker namespace>
Configure the mapping in your custom
values.yaml
file.hivemq: configMaps: - name: hivemq-logback path: /opt/hivemq/conf
The readiness probe is checking the /opt/hivemq/log/hivemq.log
file. If you change the name of the "hivemq.log" file to something else, the readiness probe will fail.
Related articles
, multiple selections available,
Related content
Override the Default logback.xml with the HiveMQ Platform Operator
Override the Default logback.xml with the HiveMQ Platform Operator
More like this
Overriding HiveMQ's Config.xml with HiveMQ Platform Operator
Overriding HiveMQ's Config.xml with HiveMQ Platform Operator
More like this
Set custom variables using Kubernetes Legacy HiveMQ operator
Set custom variables using Kubernetes Legacy HiveMQ operator
More like this
Add custom annotations in Legacy HiveMQ Kubernetes operator
Add custom annotations in Legacy HiveMQ Kubernetes operator
More like this
Restart a cluster best practice
Restart a cluster best practice
More like this
Configuring the HiveMQ Platform for One Pod per Kubernetes Node
Configuring the HiveMQ Platform for One Pod per Kubernetes Node
More like this