HiveMQ Platform Operator for Kubernetes 1.7.0 is now available!

The HiveMQ Team is excited to announce the release of HiveMQ Platform Operator for Kubernetes Operator 1.7.0. This release enhances monitoring with a new Grafana dashboard, optimizes memory usage, adds new configuration options for the HiveMQ Helm charts, and includes additional bug fixes and improvements for the HiveMQ Platform Operator.

Highlights

• Extended monitoring capabilities for the HiveMQ Platform Operator

New Monitoring Dashboard for the HiveMQ Platform Operator

The HiveMQ Platform Operator 1.7.0 Helm chart introduces a new Grafana dashboard with expanded monitoring capabilities for both the operator process and associated HiveMQ Platform deployments. The updated dashboard offers key insights, including uptime, start time, and heap usage of the operator process.

The dashboard also provides detailed views to monitor the state of your HiveMQ Platform clusters from the operator's perspective. The image below shows how your HiveMQ Platform performs a rolling restart in response to a configuration change.

Use the dashboard for a comprehensive overview of all HiveMQ Platform states the operator manages.

To enable monitoring for your HiveMQ Platform Operator and your HiveMQ Platforms, refer to the installation instructions in our documentation.

Additional Features and Improvements

HiveMQ Platform Operator Helm Charts

• Added the option to configure custom labels and annotations for the HiveMQ Platform CustomResource, HiveMQ configuration ConfigMap and Secret, and HiveMQ license Secret.
• Added the ability to use plain content data in the HiveMQ license Secret to support placeholder replacement with tools such as ArgoCD.
• Switched configuration properties and HTTP endpoints from Quarkus to HiveMQ.

HiveMQ Platform Operator for Kubernetes

• Removed the Quarkus framework to improve control over application lifecycle and dependency management. This optimization significantly reduces dependencies and loaded classes, cutting startup time by half.
• Addressed reported OOM kills caused by a slow memory leak.
• Improved the way RBAC permissions are created for the HiveMQ Platform Operator. When the operator is configured to watch a list of namespaces, the permissions are now only created for the selected namespaces instead of cluster-wide.
• Improved the security of the HiveMQ Platform Operator Init App REST API by restricting access to localhost connections.
• Fixed an issue with latency spikes in the reconciliation when the HiveMQ Platform Operator Init App is updated in the HiveMQ Platform pods.

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.