Use Tanzu Mission Control to install a Helm chart on a cluster or cluster group from a Git repository.
Prerequisites
Log in to the Tanzu Mission Control console.
Make sure you have the appropriate permissions.
- To install a Helm chart on a cluster, you must be associated with the
cluster.edit
role. - To install a Helm chart on a cluster group, you must be associated with the
clustergroup.edit
role.
The Helm service must already be enabled on a cluster to be able to install a Helm chart. For more information, see Enable Helm Service on Your Cluster or Cluster Group.
Note: Clusters running Kubernetes version 1.25 and later with pod security admission (PSA) enabled require the labels listed below in the target namespaces where your Helm release deploys pods.
Tanzu Mission Control adds these labels to the default namespace (
tanzu-helm-resources
) but you must add them to any non-default namespaces where your Helm release deploys pods.
pod-security.kubernetes.io/audit: privileged
pod-security.kubernetes.io/audit-version: latest
pod-security.kubernetes.io/enforce: privileged
pod-security.kubernetes.io/enforce-version: latest
pod-security.kubernetes.io/warn: privileged
pod-security.kubernetes.io/warn-version: latest
For Tanzu Kubernetes Grid Service clusters running in vSphere with Tanzu that have pod security policies, make sure you have the appropriate role bindings on the workload cluster. Without the appropriate permissions, Helm releases fail to be deployed. For information about creating role bindings, see Example Role Bindings for Pod Security Policy in the vSphere with Tanzu Configuration and Management documentation.