Upgrading both HiveMQ and the k8s operator (WIP)

Prerequisites:

1. k8s version 1.16+ is installed

2. Helm version 3 is installed

3. Hivemq k8s operator repo is already added

Expected Result:

Here we will show the necessary steps for a zero downtime upgrade of both the HiveMQ k8s operator as well as HiveMQ itself.

Upgrade hivemq version without downtime. Hivemq version 4.6.4 should be running without error using k8s operator version 0.9.2

Steps to follow:

Hivemq cluster values file:

apiVersion: hivemq.com/v1
kind: HiveMQCluster
metadata:
  name: hivemq-dev
spec:
  env:
  - name: TEST_ENV
    value: 'set'

operator values file: 

monitoring:
  enabled: true
operator:
  admissionWebhooks:
    enabled: false
    failurePolicy: Fail
  deployCr: false
  logLevel: DEBUG

1. Deploy Hivemq operator with 0.8.7

   1. helm upgrade --install -f operator.yaml <release name> hivemq/hivemq-operator —version 0.8.7

2. Apply Hivemq cluster with hivemq 4.6.2

   1. 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.

   1. 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

   1. 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

   1. Kubectl apply -f <hivemq cluster.yaml>

7. check the pods status(no errors)

   1. kubectl get pods

8. Update operaor version i.e 0.9.2 in cluster(operator config File)

9. Run following command for rolling upgrade

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