Page Comparison

...

1. k8s version 1.16+ is installed

2. Helm version 3 is installed

3. The Hivemq k8s operator repo is already added in helm repo

...

Instructions:

Here In the following guide, we will show outline the necessary essential steps for performing a zero-downtime upgrade of both the HiveMQ Kubernetes (k8s) operator as well as and HiveMQ itself.

Upgrade hivemq version without downtime. Hivemq By carefully following the instructions below, you will be able to successfully upgrade to HiveMQ version 4.6.4 should be running without error using , and ensure that it is running smoothly with the k8s operator version 0.9.2.

Steps to follow:

Example of hivemq-cluster.yaml file:

...

1. Deploy Hivemq operator with 0.8.7

   Code Block
   language bash
   helm upgrade --version 0.8.7 --install -f operator.yaml <release name> hivemq/hivemq-operator

2. Apply Deploy Hivemq cluster with hivemq 4.6.2

   Code Block
   language bash
   kubectl apply -f <hivemq-cluster.yaml>

3. Simply apply the new CRD using the following command (considering k8s version is 1.16+)
   Note: This step can be skipped if you are using BladeCenter.

   Code Block
   language bash
   kubectl apply -f https://raw.githubusercontent.com/hivemq/helm-charts/prerelease-4.6.4/charts/hivemq-operator/crds/hivemq-cluster.yaml

4. Scale operator to 0 so it doesn’t immediately reconcile. This will only remove the operator pod, but leave the HiveMQ nodes as remaining

   Code Block
   kubectl scale —replicas=0 deployment <operator name>

5. Edit hivemq cluster yaml to update the hivemq version as 4.6.4

6. Apply the changes

   Code Block
   Kubectl apply -f <hivemq cluster.yaml>

7. check the pods status(no errors)

   Code Block
   kubectl get pods

8. Update operator version i.e 0.9.2 in the cluster(operator config File or command line)

9. Run the following command for a rolling upgrade

   Code Block
   helm upgrade --version 0.9.2 --install -f operator.yaml <release name> hivemq/hivemq-operator

...