Applications Deployment CLI vs UI
When installing DKP, an AppDeployment resource is created for each enabled Platform Application. This AppDeployment resource references a ClusterApp, which then references the repository that contains a concrete declarative and preconfigured setup of an application, usually in the form of a HelmRelease. ClusterApps are cluster-scoped so that these Platform Applications are deployable to all Workspaces or Projects. Also refer to AppDeployment Resources from the Day 2 section of the Documentation.
Applications can be enabled and configured using the UI or CLI at both levels:
Workspace level for all clusters in a Workspace
Cluster level for specific clusters within a Workspace.
See the following table for an overview:
Desired level of configuration | CLI | UI |
|---|---|---|
Cluster-scoped deployment | Create an AppDeployment, and specify target clusters in | Go to target workspace and enable through the application card, selecting the target clusters. |
Workspace-scoped deployment | Create an AppDeployment without a | Go to target workspace and enable through the application card, selecting all target clusters. |
Cluster-scoped customization | Create an AppDeployment, and specify target clusters in | Go to target workspace and enable through the application card. Select the target clusters, and establish customizations in the configuration service per cluster. |
Workspace-scoped customization | Create an AppDeployment without a | Go to target workspace and enable through the application card. Manually select all clusters and copy-paste the customization in the configuration service for all clusters. |