Upgrading Connectware to 2.0.6 (Kubernetes)
How to upgrade Connectware to version 2.0.6 on Kubernetes.
Connectware 2.0.6 fixes an issue with SystemState functionality on agents.
Disclaimer
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
Upgrading Procedure
If your installation is older than 2.0.5, first complete the upgrade to 2.0.5 before upgrading to 2.0.6.
Update the existing 2.0.5 deployment of the auth-server to use the 2.0.6 image and wait until the process is complete:
To verify that the auth-server is fully initialized, check for the Connectware service bootstrap completed log line in each auth-server container after its restart.
Download and install Connectware 2.0.6. For more information, see Upgrading Connectware (Kubernetes).
If your agents are managed by separate Helm installations, upgrade those agents to version 2.0.6 as well. For more information, see Upgrading the connectware-agent Helm Chart.
Last updated
Was this helpful?

