Upgrade DKP
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.
Supported Upgrade Paths
Use this table to determine your correct upgrade path:
| Upgrading from Release… | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
…to | 2.1.0 | 2.1.1 | 2.1.2 | 2.1.3 | 2.1.4 | 2.2.0 | 2.2.1 | 2.2.2 | 2.2.3 | 2.3.0 | 2.3.1 | 2.3.2 | 2.3.3 | 2.4.0 | 2.4.1 | 2.4.2 | 2.5.0 | |
2.2.0 | Yes | Yes | No | No | No | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | |
2.2.1 | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | |
2.2.2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | |
2.2.3 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | NA | NA | NA | |
2.3.0 | No | No | No | No | No | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | NA | NA | |
2.3.1 | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | NA | |
2.3.2 | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | NA | |
2.3.3 | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | NA | NA | |
2.4.0 | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | NA | NA | NA | NA | |
2.4.1 | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | NA | NA | NA | |
2.4.2 | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | NA | NA | |
2.5.0 | No | No | No | No | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | NA | |
2.5.1 | No | No | No | No | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | |
2.5.2 | No | No | No | No | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | |
Understand the Upgrade Process
For this release, you perform the upgrade sequentially, beginning with the DKP UI and then moving to upgrading clusters and CAPI components.
When upgrading DKP, the process is different depending on whether you run a stand-alone Management Cluster, or a multi-cluster environment that includes a combination of a Management cluster and managed or attached workspace clusters.
Start with your Management Cluster in the UI, and then, if more than one exists, proceed workspace by workspace until complete. You can then move to upgrading Konvoy, cluster by cluster.
The overall process for upgrading to the latest version of DKP is done on each Workspace or cluster, with the following processes:
Before upgrading, we strongly recommend reading the release notes and verifying your current setup against any possible breaking changes.
For this version of DKP, it is extremely important that you review the list of major Kubernetes changes that may affect your system.
For Kommander, on your Management Cluster:
Upgrade DKP UI and all Platform Applications.
If you do not have any managed or attached clusters, skip to upgrading Konvoy on your Management Cluster.
On your Workspaces (which include Management Cluster and managed or attached clusters):
Upgrade your Workspaces, which upgrades all Platform Applications on your managed or attached workspace clusters.
Upgrade all DKP Catalog applications deployed to Workspaces.
Upgrade all DKP Catalog applications deployed to Projects.
Verify any Custom Catalog applications and ensure they are compatible with the Kubernetes version included in the new release.
For Konvoy, on your Management Cluster:
Upgrade CAPI components (Essential or Enterprise section). This upgrades the CAPI controllers, which only run on the Management Cluster.
Upgrade the Core Addons (Essential or Enterprise section). This upgrades multiple addons such as CSI, CNI, Cluster Autoscaler, and Node Feature Discovery.
Upgrade the Kubernetes version (Essential or Enterprise section). This upgrades your cluster’s control plane and node pools.
If you do not have any managed or attached clusters, you have finished the upgrade process and can start testing your environment. If you have managed or attached clusters, continue with the next section.
For Konvoy, on your Managed Clusters:
Upgrade the Core Addons. This upgrades multiple addons such as CSI, CNI, Cluster Autoscaler, and Node Feature Discovery.
Upgrade the Kubernetes version. This upgrades your cluster’s control plane and node pools. We recommend you upgrade your Kubernetes version on any attached clusters.