You can select from available Helm charts to install on a cluster.
Prerequisites
Log in to the Tanzu Mission Control console.
- To create a Helm release, you must be associated with the
cluster.edit
role.
The Helm service must already be enabled to be able to install Helm releases on a cluster. For more information, see Enable Helm Service on Your Cluster.
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.
Procedure
Results
The release is created and Tanzu Mission Control displays the installed Helm releases, showing the details.