Deploy platform applications to attached clusters using the CLI

This topic describes how to use the CLI to enable an application to deploy to attached clusters within a workspace.

See Workspace Platform Applications for a list of all applications and those that are enabled by default.

To use the DKP UI to enable applications, see Customize a workspace’s applications. To deploy an application to selected clusters within a workspace, refer to the cluster-scoped configuration section.

Prerequisites

Before you begin, you must have:

  • Set the WORKSPACE_NAMESPACE environment variable to the name of the workspace’s namespace where the cluster is attached:

    export WORKSPACE_NAMESPACE=<workspace_namespace>
    BASH
  • Set the WORKSPACE_NAME environment variable to the name of the workspace where the cluster is attached:

    export WORKSPACE_NAME=<workspace_name>
    BASH

From the CLI, you can enable applications to deploy in the workspace. Verify that an application has successfully deployed via the CLI.

Create the AppDeployment to Enable the Application

If you have already created an AppDeployment and you only want to edit the configuration to customize your application, refer to the AppDeployment Customization instructions. If you want to enable or customize your application on selected clusters within a workspace, refer to the cluster-scoped configuration instructions.

Review the list of available applications that can be enabled to deploy to your cluster. Copy the app name of the application you want to deploy.

Enable a supported application to deploy to your existing attached or managed cluster with an AppDeployment resource:

  1. Run the following command and define the --app flag to specify which platform application will be enabled:

    dkp create appdeployment istio --app istio-1.14.1 --workspace ${WORKSPACE_NAME}
    CODE
  • The --app flag must match the APP NAME from the list of available platform applications.

  • Observe that the dkp create command must be run with the WORKSPACE_NAME instead of the WORKSPACE_NAMESPACE flag.

This instructs Kommander to create and deploy the AppDeployment to the KommanderClusters in the specified WORKSPACE_NAME.

Verify Applications

The applications are now enabled. Connect to the attached cluster and watch the HelmReleases to verify the deployment. In this example, we are checking if istio got deployed correctly:

kubectl get helmreleases istio -n ${WORKSPACE_NAMESPACE} -w
CODE

You should eventually see the HelmRelease marked as Ready:

NAMESPACE               NAME        READY   STATUS                             AGE
workspace-test-vjsfq    istio       True    Release reconciliation succeeded   7m3s
CODE

Some supported applications have dependencies on other applications. See Workspace Platform Application Dependencies for that table.