What are Apps
Free, Dev, Prod, and Scale are vCluster Platform license plans. Open source does not need a license or a Platform connection. See Compare open source and free tiers.
What are Apps?​
Apps in vCluster Platform are a way for admins to package applications and scripts in consumable packages. These Apps can then be deployed into clusters, spaces, or clusters.
For example, an admin can package the cert-manager Helm chart as an App, so users can deploy the cert-manager controller into their clusters.
Apps can be an existing or custom (user provided) Helm chart, a Kubernetes manifest, or a bash
script that installs resources into a given destination (cluster, namespace, or control plane cluster).
Each App deploys exactly one of these. An App that sets more than one is rejected with
an app deploys exactly one of chart, manifests or bash.
Importantly, Apps can have parameters, that is, values that a user can provide to modify the
deployment of an application.
A new platform installation includes three example Apps, one each for a Helm chart, a Kubernetes manifest, and a bash script. Depending on your license, the platform also creates the Apps that certified Stacks use. Earlier versions also shipped ready-to-use Apps for tools such as Argo CD, cert-manager, and jsPolicy. vCluster Platform v5.0 no longer creates them. An upgraded platform keeps its existing copies, but they don't receive updates. To get updates, or to use one of these tools on a new installation, create your own App from its Helm chart.
Don't delete one of these copies while an app instance or template still references it. The instance stops reconciling until an App with that name exists again.
An overly simple and silly App example, could be an app that simply installs a ConfigMap into the given destination. This app could accept input parameters from a user to modify the contents of the ConfigMap. For example, the ConfigMap could contain a data field 'env', with a default value of 'dev'. An administrator could configure the app to accept a parameter called 'env' that has three valid values 'dev', 'test', 'stage'. When a user deploys this app, they will be prompted to select a value from the administrator provided values for this 'env' parameter. The administrator can then refer to this parameter in the ConfigMap manifest, properly setting the environment based on the user input.
This is a simple, contrived, example of an app, but they can be much more elaborate and powerful. Apps can give administrators a very flexible way to constrain what resources can be deployed into clusters, while still affording users some flexibility by exposing parameters to customize the app deployment.
An App is independently reconciled. When several applications need dependency ordering, health gates, or values from earlier applications, group them in a Stack. A Stack task can create an AppInstance from an existing App.
If an app instance doesn't deploy the way you expect, see App sync failures.