KubeMQ
DeployUpgrade and migrate

Move from legacy KubeMQ

For teams on KubeMQ v2 and v3 up to v3.1.x, the older kubemq image or kubemq-io/charts Helm charts: what changes and how to get a guided migration.

Legacy KubeMQ is KubeMQ v2 and v3 up to v3.1.x: the older kubemq image and the kubemq-io/charts Helm charts. Moving to the current release is a new installation plus a switch of your application traffic. KubeMQ support guides each move.

What changes when you move?

  • New artifact names. The current release uses the kubemq-next image and chart; see Requirements and supported setups. The latest tag of the kubemq image is a legacy build, listed in Legacy KubeMQ (kubemq image).
  • A new Kubernetes API group. The current operator manages only next.kubemq.io/v1 resources and does not adopt a legacy core.k8s.kubemq.io cluster, so both can run in one Kubernetes cluster. Name the group in kubectl: kubemqclusters.next.kubemq.io or kubemqclusters.core.k8s.kubemq.io.
  • New licensing. Legacy licenses are not carried over; see Plans compared. Remove any license block from old configuration files: the server refuses to start with one.
  • Connectors by manifest. Connectors are installed from a KubemqConnector manifest, not from connector charts; see Connectors.
  • kmq replaces kubemqctl. See Install with kmq.
  • Your clients keep working. Upgrading SDKs is a separate step.
  • Security fixes only. Legacy KubeMQ gets no new features. Contact support for your version's support timeline.

How does the move work?

Install the current release beside the legacy one, with Install on Kubernetes or, for one server, Install with Docker. Run both and move your applications pattern by pattern. Retire the legacy installation once its queues are drained; no data is copied between the two. Support plans the order of the move with you.

Unsupported setups (servers on hosts, Docker clusters, Kubernetes without the operator) follow the same path; see Requirements and supported setups.

How do I get a guided migration?

Email KubeMQ support with:

  • the image or chart you run, and its version
  • where it runs: Kubernetes or Docker, and how many servers
  • the messaging patterns and connectors you use
  • your target date

To buy a license, see Plans compared.

Was this page helpful?

Upgrade KubeMQ

Upgrade KubeMQ to the latest release with kmq, Docker, Compose or Helm, check what you run, roll back safely and leave the old combined chart.

Migrate from another broker

Next Page

On this page

What changes when you move?How does the move work?How do I get a guided migration?Related