HiveMQ platform operator pod fails to start

Problem

When attempting to deploy the HiveMQ Platform Operator with default values, you may encounter a failure where the operator’s pod continuously retries to restart.

Solution

Starting from Platform Operator version 1.1.0, there has been a slight increase in the memory requirements for the operator. To resolve this issue, you need to allocate more resources to the operator pod.

Update the operator.yaml file with the following resource specifications: Full values.yaml

          resources:
              cpu: "1024m"
              memory: "1024M"

Adjusting these values should provide the necessary resources for the operator pod to start successfully and run without issues.

Example Helm command

helm upgrade my-operator --install hivemq/hivemq-platform-operator --set resources.cpu=1024m --set resources.memory=1024M

HiveMQ Knowledge Base - Self Managed Offering

HiveMQ platform operator pod fails to start

Analytics

Problem

Solution

Example Helm command

Related articles

Related content