How KubeMQ versions work
The numbering history of KubeMQ releases, why the current product jumped from 1.3 to 3.3, and how the legacy kubemq image and charts differ.
KubeMQ has two product lines, and each has its own version numbers. This page explains how those numbers fit together. For the artifact names, what -next means and how to pin a release, see Artifacts and versions.
The current product
The current product ships as the -next artifacts: the kubemq-next server image, the kubemq-operator-next operator image and the kubemq-next Helm chart, together with the kmq command-line tool.
- Numbered 1.0 to 1.3 at first. The first releases, from September 18 to 21, 2026, were numbered 1.0.0 to 1.3.2. Their notes are on Releases 1.0–1.3.
- Renumbered at 3.3.0. The release of September 23, 2026 was numbered 3.3.0, above every legacy release, so a current version number never matches a legacy one. No server release was numbered between 1.3.2 and 3.3.0.
- kmq and the server share one number from 3.5.0. There is no server release 3.4.0. The operator and the Helm chart keep their own numbers, and each release page lists the operator and chart that go with it.
The legacy product
The legacy product is the kubemq server image, numbered v2 through v3.1.x, and the Helm charts in kubemq-io/charts. It is a separate product line, even where its numbers look close to current ones: legacy v3.1.4 is not an earlier release of current 3.3.0. Its history is on Legacy KubeMQ (kubemq image). To move to the current product, see Move from legacy KubeMQ.
Was this page helpful?