HiveMQ Platform Operator for Kubernetes 1.4.0 is now available!

The HiveMQ Team is excited to announce the release of Kubernetes Operator 1.4.0. This release adds configuration options for PersistentVolumeClaims and sidecar containers, expanded permission configuration options, and several other improvements and useful bug fixes.

Highlights

HiveMQ Platform Helm chart adds support for PersistentVolumeClaims.

HiveMQ Platform Helm chart support for PersistentVolumeClaims

PersistentVolumes allow you to mount a high-performance disk to your HiveMQ Platform containers. This ability benefits use cases that require higher IOPS (Input/Output Operations Per Second) performance. Check your Kubernetes cluster to see which storage options are available. For example, services such as Azure AKS provide a managed-premium StorageClass with higher IOPS performance depending on your selected disk size.

How it works

First, check to see which StorageClass options are available on your Kubernetes cluster:

kubectl get storageclasses.storage.k8s.io

Next, configure your HiveMQ Platform Helm chart to include PersistentVolumeClaims and mount the Volume to a path in your HiveMQ Platform container:

additionalVolumes:
  - type: persistentVolumeClaim
    name: data
    path: /opt/hivemq/data

volumeClaimTemplates:
  - kind: PersistentVolumeClaim
    apiVersion: v1
    metadata:
      name: data
    spec:
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 100Gi
      volumeMode: Filesystem
      storageClassName: standard

The new volumeClaimTemplates configuration item allows you to specify one or more PersistentVolumeClaims. Any valid Kubernetes PersistentVolumeClaim options can be used.

The additionalVolumes configuration lets you specify how the requested PersistentVolume is mounted into the file system of the HiveMQ Platform container inside the pod. Mounting the volume to the data directory means that HiveMQ persistence will benefit from higher IOPS performance.

Note: Once the Kubernetes StatefulSet controller creates a PersistentVolumeClaim it cannot be reconfigured. The HiveMQ Platform Operator cannot successfully apply changes to the volumeClaimTemplates in the Helm chart. Such changes result in a blocked rolling restart of your HiveMQ Platform. To resolve the issue, revert to the previous volumeClaimTemplates configuration. This issue is a known limitation in the way Kubernetes handles PersistentVolumesClaims that are attached to StatefulSets.

How it helps

In the example configuration, we mount the PersistentVolume to the /opt/hivemq/data directory so that the HiveMQ process benefits from the faster IOPS performance of the mounted PersistentVolume.

Additional Features and Improvements

HiveMQ Platform Operator for Kubernetes Helm charts

• Sidecar Support: You can now use HiveMQ Helm charts to configure sidecar containers that run alongside the main HiveMQ container in the same Platform Pod. All valid Kubernetes container configurations are supported.
• PersistentVolume Support: The HiveMQ Helm charts now provide configuration options for PersistentVolumeClaims.
• Added configuration option to disable the automatic creation and validation of a ServiceAccount and RBAC permissions for the HiveMQ Platform Pods. When disabled, the HiveMQ Platform Operator starts with fewer permissions and relies on manual configuration of a ServiceAccount by the customer.

HiveMQ Platform Operator for Kubernetes

• Fixed an issue with missing Kubernetes permissions for the HiveMQ Platform Pods when the HiveMQ Platform Operator is not running.
• Fixed an issue when a ConfigMap for a custom extension has no config.xml entry.
• Fixed an issue to ensure a rolling restart when a StatefulSet is recreated.

Get Started Today

To get started with the new HiveMQ Platform Operator, see our HiveMQ Platform Operator Quick Start Guide.

To update from a previous version of the HiveMQ Platform Operator for Kubernetes, you need to update your HiveMQ Platform custom resource definition (CRD). For step-by-step instructions, see our Upgrade Guide.

To learn more about our new operator, see HiveMQ Platform Operator for Kubernetes.