Essential: Upgrade the Essential Cluster and Platform Applications
This section describes how to upgrade your Kommander Management cluster and all Platform Applications to their supported versions in air-gapped, non-air-gapped and on-prem environments. To prevent compatibility issues, you must first upgrade the Kommander component on your Essential Cluster before upgrading to DKP.
It is important you upgrade Kommander BEFORE upgrading the Kubernetes version. This ensures that any changes required for new or changed Kubernetes API’s are already present.
Upgrade Kommander
Prerequisite
Use the
--kubeconfig=${CLUSTER_NAME}.conf
flag or set theKUBECONFIG
environment variable to ensure that you upgrade Kommander on the right cluster. For alternatives and recommendations around setting your context, refer to Provide Context for Commands with a kubeconfig File.If you have DKP Insights installed, ensure you uninstall it before upgrading DKP. See DKP Insights Upgrade to 1.0.0 (DKP 2.7.0) for more information.
Limited availability of DKP resources
If you have configured a custom domain, running the
upgrade
command could result in an inaccessibility of your services via your custom domain for a few minutes.The DKP UI and other APIs may be inconsistent or unavailable until the upgrade is complete.
Upgrade
Use the DKP CLI to upgrade Kommander and all the Platform Applications in the Management Cluster:
Troubleshooting
If the upgrade fails, run the following command to get more information on the upgrade process:
CODEdkp upgrade kommander -v 6
If you find any
HelmReleases
in a “broken” release state such as “exhausted” or “another rollback/release in progress”, you can trigger a reconciliation of theHelmRelease
using the following commands:CODEkubectl -n kommander patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": true}]' kubectl -n kommander patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": false}]'