Manage Kubernetes Installed Applications

​

Introduction

An Installed Application is a running instance of a Kubernetes app (Helm chart) on a specific cluster. An Installed Application differs from a Marketplace app: the Marketplace holds the app blueprint, while an Installed Application is the deployed instance on a cluster. Before you can install a chart, it must be imported into your organization’s library. Charts are imported from the Kubernetes section of the Marketplace Catalog. After import, the chart appears in My Library and becomes available in the Install Application wizard.

• If the chart is not yet in your library: Go to the Marketplace Catalog, find the chart, and import it. Then return to the Kubernetes Apps tab to install it.
• If the chart is already in your library: Go directly to the Kubernetes Apps tab and select it from the Install Application wizard.

This article covers the Installed Applications workflow. For instructions on importing charts, see Manage Apps from the Kubernetes Marketplace.

​

Install an Application

To install an application:

1. In the sidebar, select Infrastructure > Workloads > Applications. Select the Kubernetes Apps tab.
2. Select Install Application.
3. Complete the three-step wizard described in the following sections.

​

Details

1. Under Application, select the app in the Kubernetes App field and choose a version in the Version field.
2. Under Application, select the app in the Kubernetes App field and choose a version in the Version field.
3. Under General, enter a value in the Install Name field (the unique identifier) and the Install Title field (the display name). Optionally, enter a Description.
4. Under Assignment, select a Project. To filter the target cluster list, add one or more values in the Cluster Tags field. Only clusters that match all specified tags appear in the Target Cluster table.
5. In the Target Cluster table, select the cluster to deploy to. The table shows Name, Status, Kubernetes Version, No. of Nodes, and Project for each cluster. Only clusters that run Kubernetes are listed. This means clusters created in ZEDEDA Edge Kubernetes Service mode and imported clusters. A cluster that has not reported its Kubernetes version shows a dash in that column.
6. Select Continue.

​

Values

1. Review and adjust the Helm chart configuration using one of the available tabs:
   • Edit Options: Modify values using a structured form.
   • Edit YAML: Edit the values file directly as YAML.
   • Compare Changes: Review your changes against the defaults using the Unified or Split view.
2. Select Review.

​

Review

1. Review the full deployment configuration.
2. Select Install App to deploy the application.

The application appears in the Installed Applications list. Initial status might show Unknown while the deployment propagates to the cluster.

​

View Installation Status

The Installed Applications list shows the following columns: Name, Status, Helm Chart, Cluster, and Timestamp. Status values are: Select an application name to open its detail page. The detail page has two tabs:

• Status tab: Shows Status, Age, and Created By. The Resources table lists each resource with its State, API Version, Kind, and Name.
• Details tab: Shows the full configuration including Name, ID, Title, Description, Helm Chart, Cluster, Namespace, Created, Updated, Tags, and the deployed Values as YAML.

​

Edit an Installed Application

1. In the Installed Applications list, open the row menu for the application you want to change.
2. Select Edit.
3. Update the Title, Namespace, Values (YAML), or Description as needed.
4. Select Save.

Saving triggers a re-deploy of the application with the updated configuration. The status transitions back through Unknown or Not Ready while the cluster applies the changes.

​

Delete an Installed Application

1. In the Installed Applications list, open the row menu for the application you want to remove.
2. Select Delete.
3. Confirm the deletion.

Deleting an Installed Application removes the running instance from the cluster. The Marketplace blueprint is not affected.

​

Next Steps