Install using helm chart -getting status failed

1

while doing installation using helm charts getting status failed with a message ,failed to apply deployment .

image
image1455×161 35.4 KB

Also i had tried with various version of HiveMQ from helm chart and still getting the same issue .

2

Hello @bismay,

Welcome to the HiveMQ community forum.

Can you please help with the following details to take a look?

  • Kubernetes version used for deploying hivemq

  • Output of following commands
    helm list -n <namespace>
    kubectl get all -n <namespace>

    In case, pods are stuck with the status pending or error
    kubectl describe pod <pod name> -n

  • your custom values.yaml

Regards,
Sheetal from HiveMQ team

3

Hi HiveMQ,

  1. Can you provide the resource details of GKE cluster for creation of hiveMQ in both staging and production ( minimum requirement for cluster creation and custom values used)

  2. pods are not created. below error i was getting .

does not have minimum availability

3.4. kubectl get all -n -

image.png
image.png1599×524 109 KB

  1. custom values.yaml file - (i am running by default not any custom values )

waiting for reply

4

Hello @bismay

Thank you for sharing the details. From the output of kubectl get all command, we see that hivemq pods are stuck with Pending status.

You can check the events of any of the hivemq pods which can help why it is stuck in Pending.
kubectl describe pod <pod-name>
Please share the output of this command with us to take a look.

Also, make sure you have enough resources to setup 3 node cluster( in your case. 12 CPU’s and 12GB RAM). the minimum hardware requirements per node for HiveMQ broker to run as follow,

  • At least 4 GB of RAM
  • 4 or more CPUs
  • 100 GB or more free disk space.

Regards,
Sheetal from HiveMQ team

5

Hello,
Helm deployment is not succeeding in kubernetes, what are the best way to make it work ?

6

Hello @kaushal

Welcome to the HiveMQ community forum.

To troubleshoot and resolve a failed Helm deployment of HiveMQ in Kubernetes, follow these best practices:

1. Check Helm Chart Values:

  • Review the values.yaml file for correct configurations such as resource requests, limits, and storage settings.

2. Kubernetes Logs & Events:

  • Check the logs of the failing HiveMQ pods using kubectl logs <pod-name>. Pay attention to errors related to network, storage, or configuration.
  • Review Kubernetes events to get insights on what went wrong during the Helm deployment with kubectl describe pod <pod-name> or kubectl get events.

3. HiveMQ logs:

  • Check hivemq.log from hivemq pod and confirm if there are no WARN or ERRORs logged.

Following these steps should help identify and resolve the issues causing the Helm deployment to fail.

We suggest following our documentation for the successful deployment of HiveMQ using Legacy or new platform operator.

In case you need help. Feel free to reach us back with sharing steps to reproduce(exact commands), values.yaml and error details.

Kind regards,
Sheetal from HiveMQ Team