.png)
Upgrade DKP
DKP Upgrade Path
The DKP upgrade represents an important step of your environment’s lifecycle, as it ensures that you are up-to-date with the latest features and can benefit from the most recent improvements, enhanced cluster management, and better performance. This section describes how to upgrade your air-gapped and non-air-gapped environment to the latest version of DKP compatible with the latest Kubernetes version.
Prerequisite
Check what version of DKP you have downloaded currently using cli command dkp version.
dkp versionSupported Upgrade Paths:
Use this table to determine your correct upgrade path:
Upgrading from Release… | ||||||||
|---|---|---|---|---|---|---|---|---|
…to Release | 2.4.0 | 2.4.1 | 2.5.0 | 2.5.1 | 2.5.2 | 2.6.0 | 2.6.1 | |
2.4.0 | NA | NA | NA | NA | NA | NA | NA | |
2.4.1 | Yes | NA | NA | NA | NA | NA | NA | |
2.5.0 | Yes | Yes | NA | NA | NA | NA | NA | |
2.5.1 | Yes | Yes | Yes | NA | NA | NA | NA | |
2.5.2 | Yes | Yes | Yes | Yes | NA | NA | NA | |
2.6.0 | No | No | Yes | Yes | Yes | NA | NA | |
2.6.1 | No | No | Yes | Yes | Yes | Yes | NA | |
2.6.2 | No | No | Yes | Yes | Yes | Yes | Yes | |
Upgrade Order
Perform the upgrade sequentially, beginning with the Kommander component and then moving to upgrading clusters and CAPI components in the Konvoy component.
When upgrading your entire DKP product, the process is different depending on your environment.
Enterprise: A multi-cluster environment that includes a combination of a Management cluster(s) and Managed or Attached workspace clusters.
Before upgrading, we strongly recommend reading the release notes and verifying your current setup against any possible breaking changes.
Review the list of major Kubernetes changes that may affect your system.