Page Comparison

...

1. Update values.yaml Configuration: Open the hivemq-platform’s values.yaml file and verify/update the following configurations:

   Code Block
   language yaml
   config: create: false name: "my-config" overrideHiveMQConfig: "" overrideStatefulSet: ""

   • create: false: Disable the creation of the default HiveMQ config.xml file.

   • name: "my-config": Specify a custom name for the ConfigMap.

   • overrideHiveMQConfig: "" and overrideStatefulSet: "": Ensure that HiveMQ config and StatefulSet are is not overridden here.

2. Create Custom ConfigMap: Use the provided manifest cm-my-config.yaml to create a new ConfigMap named my-config:

   Code Block
   language bash
   kubectl apply -f cm-my-config.yaml

   Deploy Updated HiveMQ: Deploy the updated HiveMQ platform with the modified values from the values.yaml file.

3. Verify Configuration: Confirm the presence of declared-shared-subscriptions.xml in the /opt/hivemq/conf-k8s/ directory within the HiveMQ pods:

   Code Block
   language bash
   kubectl exec pods/my-hivemq-0 -c hivemq -- \ ls -la conf-k8s/declared-shared-subscriptions.xml

4. Check hivemq.log: Ensure that the hivemq.log records the inclusion of Declared shared subscriptions:

   Code Block
   language bash
   kubectl exec pods/my-hivemq-0 -c hivemq -- \ grep -i declared log/hivemq.log

   Code Block
   language text
   INFO - Declared shared subscriptions from file /opt/hivemq/conf-k8s/declared-shared-subscriptions.xml

   Future Configuration Updates: For any future configuration updates, modify the cm-my-config.yaml manifest and apply the changes using:

   Code Block
   language bash
   kubectl apply -f cm-my-config.yaml

   This ensures that alterations to the ConfigMap are recognized, and updates are applied in a rolling manner by the operator.

...