Workspace Catalog Application Upgrades
Upgrade catalog applications using the CLI and UI
Ensure your clusters run on a supported Kubernetes version for this release of DKP, and that said Kubernetes version is also compatible with your catalog application version.
For customers with an Enterprise license and a multi-cluster environment, we recommend keeping all clusters on the same Kubernetes version. This ensures your DKP catalog application can run on all clusters in a given workspace.
Konvoy installs a new Kubernetes version with each upgrade, therefore it is important that your Catalog application is compatible with the Kubernetes version that comes with this release of DKP.
If your current Catalog application version is not compatible with this release’s Kubernetes version, upgrade the application to a compatible version BEFORE upgrading the Konvoy component on Managed clusters or BEFORE upgrading the Kubernetes version on Attached clusters.
For air-gapped environment with catalog applications only: Ensure you have updated your catalog repository before upgrading. The catalog repository should contain the Docker registry containing the DKP catalog application images and a charts bundle file containing DKP catalog applications charts.
Upgrade Catalog Applications
Before upgrading also, keep in mind the distinction between Platform applications and Catalog applications. Platform applications are deployed and upgraded as a set for each cluster or workspace. Catalog applications are deployed separately, so that you can deploy and upgrade them individually for each project.
Upgrade with UI
Follow these steps to upgrade an application from the DKP UI:
From the top menu bar, select your target workspace.
Select Applications from the sidebar menu.
Select the three dot button from the bottom-right corner of the desired application tile, and then select Edit.
Select the Version drop-down, and select a new version. This drop-down will only be available if there is a newer version to upgrade to.
Upgrade with CLI
Please note that the below commands are using the workspace name and not namespace.
You can retrieve the workspace name by running the command:
dkp get workspaces
To view a list of the deployed
apps to your workspace, you can run the command:
dkp get appdeployments --workspace=<workspace-name>
dkp upgrade catalogapp <appdeployment-name> --workspace=<my-workspace-name> --to-version=<version.number>
For example, the following command upgrades the Kafka Operator application, named
kafka-operator-abc, in a workspace to version
dkp upgrade catalogapp kafka-operator-abc --workspace=my-workspace --to-version=0.23.0-dev.0
Platform applications cannot be upgraded on a one-off basis, and must be upgraded in a single process for each workspace. If you attempt to upgrade a platform application with these commands, you receive an error and the application is not upgraded.