HiveMQ Platform Operator for Kubernetes 2.2.1 Maintenance Release

The HiveMQ Team is pleased to announce the release of the HiveMQ Platform Operator for Kubernetes 2.2.1. This maintenance release improves reliability and scalability for large-scale Kubernetes deployments, adds observability into the operator's Kubernetes API footprint, and fixes several issues.

HiveMQ Platform Operator for Kubernetes

• The operator now automatically designates the Log-Based Clustering Bootstrap node through the init-app. During a Kubernetes rolling restart, the lowest-ordinal pod rejoins the existing cluster instead of re-bootstrapping and crash-looping. The operator now owns the HIVEMQ_CLUSTERING_BOOTSTRAP environment variable, and the Helm chart rejects any customer-set value.
• Fixed rolling restarts that failed when a non-zero StatefulSet start ordinal (spec.ordinals.start) was configured. The operator now reads the configured start ordinal instead of assuming 0-based ordinals. It targets the correct pod names for rolling restarts, extension restarts, log-level changes, and init-app updates.
• Optimized Kubernetes informers for large-scale deployments. Each operator-managed informer (Cluster and Platform Services, Pods, ConfigMaps, and RoleBindings) is now scoped to only its own resources. This reduces memory use and startup load when one operator manages hundreds of platforms.
• Added Kubernetes informer metrics and Grafana dashboard panels that show the number of informer event sources, per-informer cache sizes, and informers still syncing. You can now size and monitor the operator's Kubernetes API footprint on large deployments.
• Added a fallback chain for init-app REST API calls, so the operator no longer depends on curl in the platform container image. The legacy 1.x-to-2.x update path now works on curl-free base images. It calls the pod's REST API directly over HTTP, with pod-exec fallbacks.
• Hardened the init-app update path. The operator now restores the canonical init-app JAR early during startup. This prevents a CrashLoopBackOff if the main container restarts during an update from a pre-2.2.0 version.

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.