HiveMQ Platform Operator for Kubernetes 1.5.1 Maintenance Release

The HiveMQ Team is pleased to announce the availability of HiveMQ Platform Operator for Kubernetes 1.5.1. This maintenance release for the 1.5 series provides useful bug fixes and usability enhancements.

HiveMQ Platform Operator for Kubernetes Helm charts

We added more helpful information about VolumeClaimTemplates in our documentation and the values.yaml of the HiveMQ Platform Helm chart. The new entry highlights that to mount PersistentVolumes with write file permissions, you must configure a corresponding PodSecurityContext. See the documentation or values.yaml file for an example.

TIP: After you update your Helm charts via helm repo update, enter helm show values hivemq/hivemq-platform to see the current default values.yaml of the Helm chart. The show values command lets you quickly check for new options and additional comments.

HiveMQ Platform Operator for Kubernetes

We fixed an issue when updating the HiveMQ Platform Operator from version 1.3.1 or older with a running HiveMQ Platform. In such a scenario, a second RoleBinding can be created that blocks the reconciliation. With this release, the operator automatically deletes the extraneous RoleBinding.

You can easily check the log of your HiveMQ Platform Operator pod to see if you are affected:

ERROR i.j.o.p.event.EventProcessor - Error during event processing ExecutionScope{
  resource id: ResourceID{name='release-name', namespace='platform-namespace'}, version: 12345}
  io.javaoperatorsdk.operator.OperatorException: 
  io.javaoperatorsdk.operator.AggregatedOperatorException: Exception(s) during workflow execution. Details:
  com.hivemq.platform.operator.dependants.PodRoleResource -> 
  java.lang.IllegalStateException: More than 1 secondary resource related to primary

TIP: As a workaround, until you upgrade to version 1.5.1 or above, you can manually delete the superfluous RoleBinding with the name hivemq-platform-pod-role-binding-<RELEASE-NAME> to unblock the operator. For example, via kubectl delete rolebindings -n <PLATFORM-NAMESPACE> hivemq-platform-pod-role-binding-<RELEASE-NAME>.

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 all the features our operator offers, see HiveMQ Platform Operator for Kubernetes.