🚧 Workaround for Projected Volumes with HiveMQ Platform on Kubernetes

At this time, the hivemq-platform 0.2.35 does not support additionalVolumes of type projected[x]. While support for this is on our roadmap, you can use the following manual workaround to apply projected volumes to your HiveMQ Platform deployment.

📘 Instructions

Step 1: Remove the projected volume definition from your values file

In your values.yaml file for the HiveMQ Platform Helm Chart, clear the additionalVolumes section:

additionalVolumes: []

Save the updated file as:

my-hp-values-without-av.yaml

Step 2: Generate Kubernetes manifests from the Helm chart

Run the following Helm command to generate manifests:

helm template hp hivemq/hivemq-platform \
  --values my-hp-values-without-av.yaml \
  --namespace hivemq \
  --output-dir=manifests

🟦 Replace hp with the actual release name for your HiveMQ Platform deployment.
If successful, the rendered manifests will be available in:
./manifests/hivemq-platform/templates/

Step 3: Add the projected volume manually

Open the generated file hivemq-custom-resource.yml, and navigate to the spec.statefulSet section.

Manually add:

your projected volume under volumes
the corresponding volumeMount under the container definition

Save the modified file as:

hivemq-custom-resource-with-projected.yml

Step 4: Apply the updated custom resource

Apply the updated manifest using:

kubectl apply -f hivemq-custom-resource-with-projected.yml --namespace hivemq

🟦 The HiveMQ Platform Operator will detect the change and automatically re-sync the pods.

❓ Need Help?

If you need assistance at any step, feel free to reach out to our support team.