Enterprise: Upgrade Workspace DKP Catalog Applications
Upgrade catalog applications using the CLI and UI
Considerations for Upgrading DKP Catalog Applications with Spark Operator Post DKP 2.7
Starting in DKP 2.7, the Spark operator app is removed, resulting in the complete uninstallation of the app after upgrading the DKP Catalog Applications GitRepository.
This section provides instructions on how you can continue using Spark in DKP 2.7 and after.
If you do not plan on using Spark or if you’re content with having Spark be uninstalled automatically, you can skip this section and proceed to the Update the DKP Catalog Applications GitRepository section.
Update the DKP Catalog Applications GitRepository
Follow the instructions in this section to update the GitRepository dkp-catalog-applications
.
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.
Select Save.
Repeat this process for on each workspace where you have deployed the application.
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>
To see what app(s) and app versions are available to upgrade, run the following command:
NOTE: You can reference the app version by going into the app name (e.g.<APP ID>-<APP VERSION>
)CODEkubectl get apps -n ${WORKSPACE_NAMESPACE}
You can also use this command to display the apps and app versions, for example:
CODEkubectl get apps -n ${WORKSPACE_NAMESPACE} -o jsonpath='{range .items[*]}{@.spec.appId}{"----"}{@.spec.version}{"\n"}{end}'
Below is an example of an output that shows the different apps and apps versions.
CODEkafka-operator----0.20.0 kafka-operator----0.20.2 kafka-operator----0.23.0-dev.0 zookeeper-operator----0.2.13 zookeeper-operator----0.2.14
Run the following command to upgrade an application from the DKP CLI:
CODEdkp upgrade catalogapp <appdeployment-name> --workspace=${WORKSPACE_NAME} --to-version=<version.number>
As an example, the following command upgrades the Kafka Operator application, named
kafka-operator-abc
, in a workspace to version0.25.1
:CODEdkp upgrade catalogapp kafka-operator-abc --workspace=${WORKSPACE_NAME} --to-version=0.25.1
Repeat this process for on each workspace where you have deployed the application.
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.
As of DKP 2.7, the versions of Catalog applications other than these listed below are deprecated:
kafka-operator-0.25.1
zookeeper-operator-0.2.16-dkp.1
If you plan on upgrading to DKP 2.7 or above, ensure that you upgrade these applications to the latest compatible version.
To find what versions of applications are available for upgrade, use
kubectl
:CODEkubectl get apps -n ${WORKSPACE_NAMESPACE}
For more information, see Workspace DKP Catalog Applications | Workspace DKP Catalog Applications.
To ensure you do not install images with known CVE’s, you should specify a custom image for kafka
and zookeeper
by following these instructions: