search
Contact Uscybus.io

Upgrading Connectware to 2.0.5 (Kubernetes)

How to upgrade Connectware to version 2.0.5 on Kubernetes.

Connectware 2.0.5 brings significant improvements to OPC UA reliability and CybusMQ performance, reducing message loss and improving system stability under load. For more information, see What has changed in 2.0.5.

This upgrade requires you to delete the data volumes that store the metadata of CybusMQ.

hashtag
Disclaimer

circle-exclamation

When upgrading your Connectware instance, follow the upgrade path based on your current version:

  • If you are on version 1.4.1 or below

    • Upgrade sequentially: 1.5.0 → 1.7.0 → 2.0.0 → 2.0.1 → 2.0.2 → 2.0.5 → 2.0.6

  • If you are between version 1.5.0 and 1.6.2

    • Upgrade sequentially: 1.7.0 → 2.0.0 → 2.0.1 → 2.0.2 → 2.0.5 → 2.0.6

  • If you are on version 1.7.0 or newer (but below 2.0.0)

    • Upgrade sequentially: 2.0.0 → 2.0.1 → 2.0.2 → 2.0.5 → 2.0.6

  • If you are on version 2.0.0

    • Upgrade sequentially: 2.0.1 → 2.0.2 → 2.0.5 → 2.0.6

  • If you are on version 2.0.1

    • Upgrade sequentially: 2.0.2 → 2.0.5 → 2.0.6

  • If you are on version 2.0.2, 2.0.3, or 2.0.4

    • Upgrade sequentially: 2.0.5 → 2.0.6

  • If you are on version 2.0.5

    • Upgrade directly to 2.0.6

  • If you are performing a clean or new installation

    • No upgrade path required. You can install the latest available version directly.

Detailed instructions on each upgrade step

hashtag
Important Notes

This upgrade will delete all persisted data of the Connectware broker. This includes client sessions, subscriptions, and retained data. If your configuration relies on any type of data persisted by the broker, make sure to properly initialize your applications after the upgrade.

If you rely on persisted data, create a backup or snapshot of the broker data volumes. This allows you to roll back in case of complications.

hashtag
Upgrading Procedure

circle-exclamation

If your installation is older than 2.0.2, first complete the upgrade to 2.0.2 before upgrading to 2.0.5.

  1. Scale down the broker cluster to zero replicas to stop all broker pods. For more information, see Scaling Down the Broker Cluster to Zero.

  2. Delete the broker data volume of Connectware. For more information, see Deleting Broker Data Volumes on Kubernetes.

  3. Download and install Connectware 2.0.5. For more information, see Upgrading Connectware (Kubernetes).

Once all pods are up and running again and no new deviations appear in Connectware, the upgrade has been successful.

PreviousUpgrading Connectware to 2.0.6 (Kubernetes)NextUpgrading Connectware to 2.0.2 (Kubernetes)

Last updated

Was this helpful?