Skip to content

HiveMQ Platform Operator for Kubernetes 1.2.0 Release

by HiveMQ Team
1 min read

The HiveMQ Team is excited to announce the release of Kubernetes Operator 1.2.0. This release introduces a host of new features and enhancements to streamline your Kubernetes operations. Along with the public availability of the HiveMQ Helm chart repository, this update is packed with improvements to simplify customization, enhance functionality, and provide even more versatility for managing your HiveMQ deployments.


Public availability of HiveMQ Platform Operator Helm charts

HiveMQ has just published the Helm charts of the HiveMQ Platform Operator and the HiveMQ Platform on GitHub. Now, you can access all HiveMQ Helm charts in one repository. Along with our convenient Helm charts, we have also published manifest files with default values that can be used as the basis for advanced installation without using Helm.

How it works

The HiveMQ Helm charts provide an efficient way to install the HiveMQ Platform Operator and the HiveMQ Platform.

Simply load the HiveMQ Helm charts into your local Helm installation:

helm repo add hivemq

Or, refresh your local Helm installation:

helm repo update

Next, you can easily install the HiveMQ Platform Operator and the HiveMQ Platform:

helm install <your-operator> hivemq/hivemq-platform-operator --wait && \
helm install <your-platform> hivemq/hivemq-platform

How it helps

The HiveMQ public Helm chart repository and HiveMQ documentation contain useful examples and resources to help you fully utilize the HiveMQ Platform Operator for your deployments on Kubernetes.

Added configuration options in the HiveMQ Helm charts

HiveMQ Platform Operator for Kubernetes 1.2.0 is packed full of new configuration options to expand the usability of the Helm charts. Here are a few examples of the increased capabilities:

Support for environment variables

The HiveMQ Helm charts now give you the ability to configure environment variables from a secret, ConfigMap, or directly in your Helm charts values.yaml. The environment variables are then available in the HiveMQ container.

Example environment variable configuration in the Helm chart values.yaml file:

  - name: <ENV_VAR_NAME_1>
    value: <value>
  - name: <ENV_VAR_NAME_2>
        name: my-secret
        key: my-secret-key
  - name: <ENV_VAR_NAME_3>
        name: my-config-map
        key: my-configmap-key

Added configuration options for HiveMQ

We are thrilled to introduce a brand-new HiveMQ Platform Helm chart that makes it even easier to configure and scale your HiveMQ platforms on Kubernetes in a standardized and customizable way. Now, you can configure most standard HiveMQ options directly with the HiveMQ Platform Helm chart.

Example added configuration options for HiveMQ:

    maxConnections: <value>
    maxClientIdLength: <value>
    sessionExpiryMaxInterval: <value>
    maxPacketSize: <value>
    wildcardSubscriptions: <value>
    maxQualityOfService: <value>
    retainedMessages: true
    allowEmptyClientId: <value>

Add Init containers for advanced use cases

You can now easily add Kubernetes Init containers to your configuration. Init containers help execute custom code that prepares your installation. In the following example, we download a custom JDBC driver to be used for the HiveMQ Enterprise Security Extension.

Create an init-container-jdbc.yaml file:

- name: download-mysql-driver
  image: busybox
  command: [ 'sh', '-c', 'wget -P /jdbc-driver' ]
    - name: jdbc-driver-volume
      mountPath: /jdbc-driver

Add the following section to your custom platform-values.yaml file:

- type: emptyDir
  mountName: jdbc-driver-volume
  path: /opt/hivemq/extensions/hivemq-enterprise-security-extension/drivers/jdbc

Install or upgrade your HiveMQ Platform Helm release:

helm upgrade -i <release-name> hivemq/hivemq-platform -f platform-values.yaml --set-file config.overrideInitContainers=init-container-jdbc.yaml

TIP: Starting with HiveMQ 4.25.1, the Enterprise Security Extension ships with default JDBC drivers which reduces the need to download custom JDBC drivers.

For detailed information and configuration options, check the HiveMQ Platform Operator for Kubernetes documentation.

Additional Features and Improvements

HiveMQ Platform Operator for Kubernetes Helm charts:

  • Session affinity is now enabled and set by default to ClientIP for the Control Center service.
  • Added support to configure Secure WebSockets.
  • Added the ability to add custom annotations to HiveMQ pods.
  • Fixed an issue to remove a WebSocket listener from the HiveMQ Broker configuration that is not configured.
  • Added the ability to configure environment variables with the HiveMQ Platform Helm chart.
  • Added support to configure a custom service account with the HiveMQ Platform Helm chart.
  • Added the ability to configure Init Containers in the HiveMQ Platform Operator Helm charts.
  • Adjusted the default log level from DEBUG to INFO for the HiveMQ Platform Helm chart.
  • Added the ability to configure the REST API authentication for the HiveMQ Platform Helm chart.

HiveMQ Platform Operator for Kubernetes:

  • Fixed an issue where configuration changes that do not require a rolling restart generated unnecessary monitoring alerts such as KubeStatefulSetUpdateNotRolledOut.
  • Improved the way configuration changes for HiveMQ extensions that support configuration hot-reload are handled to provide smoother operation.
  • Fixed the incorrect setting for user IDs (UID) in the HiveMQ Platform Operator Helm chart when configuring the podSecurityContext.
  • Added the ability to update the HiveMQ Platform Operator Init App during runtime without a rolling restart.
  • Fixed duplicate volume mount paths when sharing the same requestHeaderSecretName value in custom extensions.
  • Added the ability to define custom ServiceAccounts in the StatefulSet specification of HiveMQ Platform custom resources to facilitate pod permission management.
  • Fixed an issue when Kubernetes clusters use a custom domain name. The cluster service IP is automatically discovered. Configuration of custom DNS suffixes is not required.
  • Fix incorrect deletion of preloaded DNS Discovery extension in the HiveMQ Platform Operator Init App for legacy Kubernetes images.

Get Started Today

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

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

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

HiveMQ Team

The HiveMQ team loves writing about MQTT, Sparkplug, Industrial IoT, protocols, how to deploy our platform, and more. We focus on industries ranging from energy, to transportation and logistics, to automotive manufacturing. Our experts are here to help, contact us with any questions.

HiveMQ logo
Review HiveMQ on G2