# next line v1.0.0 (/release-notes/next-v1)



**v1.0.0** is the first release published as **`-next` artifacts**. These are the names every new installation uses.

<Callout type="info">
  **"next" means two things in KubeMQ.*&#x2A; **`-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.
</Callout>

## What's new [#whats-new]

* **New artifact names.** All images come from `europe-docker.pkg.dev/kubemq/images` and need no registry login:

  | Artifact            | Name                                                         |
  | ------------------- | ------------------------------------------------------------ |
  | Server image        | `kubemq-next`                                                |
  | Server image (FIPS) | `kubemq-next-fips`                                           |
  | Operator image      | `kubemq-operator-next`                                       |
  | Helm chart          | `kubemq-next` from `https://kubemq-io.github.io/charts-next` |

* **New Kubernetes API group: `next.kubemq.io/v1`**, with the kinds `KubemqCluster` and `KubemqConnector`. In `kubectl`, use the full resource names `kubemqclusters.next.kubemq.io` and `kubemqconnectors.next.kubemq.io`.

* **One Helm chart.** `kubemq-next` installs the CRDs, the operator, and one cluster in a single release. See [Install with Helm](/deploy/kubernetes-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 [#known-limitations]

* **`linux/amd64` only.** 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, set `spec.image` explicitly on every `KubemqConnector`. Connectors are installed by applying a `next.kubemq.io/v1` manifest — there are no connector Helm charts.

## Coming from legacy v2 [#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](/deploy/coming-from-legacy-v2).

## Install [#install]

```bash title="Terminal"
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](/deploy/docker).