next line v1.0.0
First release of the KubeMQ next line — new -next artifact names, the next.kubemq.io/v1 API group, one Helm chart, and version numbers that restart at v1.0.0.
v1.0.0 is the first release published as -next artifacts. These are the names every new installation uses.
"next" means two things in KubeMQ. -next artifacts and the next line are the product line for new installations. The next storage engine is the server's storage engine, selected with store.engine: next. The storage engine setting and its values (legacy, next, auto) are unchanged by this release.
What's new
-
New artifact names. All images come from
europe-docker.pkg.dev/kubemq/imagesand need no registry login:Artifact Name Server image kubemq-nextServer image (FIPS) kubemq-next-fipsOperator image kubemq-operator-nextHelm chart kubemq-nextfromhttps://kubemq-io.github.io/charts-next -
New Kubernetes API group:
next.kubemq.io/v1, with the kindsKubemqClusterandKubemqConnector. Inkubectl, use the full resource nameskubemqclusters.next.kubemq.ioandkubemqconnectors.next.kubemq.io. -
One Helm chart.
kubemq-nextinstalls the CRDs, the operator, and one cluster in a single release. See Install with Helm. -
Versions restart at v1.0.0. The server, the operator, the chart, and the kmq CLI all carry v1.0.0. These numbers are not comparable with any earlier KubeMQ version number.
-
Tags. Every image is published as an immutable release tag (
:v1.0.0) plus the moving tag:latest. There is no other channel tag. -
The kmq CLI keeps its name. Its image stays
europe-docker.pkg.dev/kubemq/images/kmq; its version becomes v1.0.0.
Known limitations
linux/amd64only. Images are not yet built for other architectures.- Connector images ship in next v1.1. The Targets, Sources, and Bridges images (
kubemq-targets-next,kubemq-sources-next,kubemq-bridges-next) are not part of v1.0.0. Until then, setspec.imageexplicitly on everyKubemqConnector. Connectors are installed by applying anext.kubemq.io/v1manifest — there are no connector Helm charts.
Coming from legacy v2
On Kubernetes, install the new chart beside the legacy installation and move traffic — there is no in-place path under the new operator. On Docker and VMs, a kubemq-next image can start on an existing v2 data directory. Legacy v2 receives security fixes only. Details: Coming from legacy v2.
Install
helm repo add kubemq-next https://kubemq-io.github.io/charts-next
helm install kubemq-next kubemq-next/kubemq-next -n kubemq --create-namespace --set key=<license-key>Or with Docker: Install with Docker.
Was this page helpful?