# Helm

To install and run Kuma on Kubernetes with Helm charts execute the following steps:

Finally you can follow the Quickstart to take it from here and continue your Kuma journey.

Please note that at least version 3.8.0 of Helm is required to use the Kuma Helm charts. If you are using an older version of Helm, please upgrade to version 3.8.0 first.

Kuma also provides an alternative Kubernetes distribution that we can use instead of Helm charts.

# Add the Kuma charts repository

To start using Kuma with Helm charts, we first need to add the Kuma charts repository (opens new window) to our local Helm deployment:

helm repo add kuma https://kumahq.github.io/charts
1

Once the repo is added, all following updates can be fetched with helm repo update.

# Run Kuma

At this point we can install and run Kuma using the following commands. We could use any Kubernetes namespace to install Kuma, by default we suggest using kuma-system:

helm install --create-namespace --namespace kuma-system kuma kuma/kuma
1

This example will run Kuma in standalone mode for a "flat" deployment, but there are more advanced deployment modes like "multi-zone".

# Use Kuma

Kuma (kuma-cp) will be installed in the newly created kuma-system namespace! Now that Kuma has been installed, you can access the control-plane via either the GUI, kubectl, the HTTP API, or the CLI:

    You will notice that Kuma automatically creates a Mesh entity with name default.

    # Quickstart

    Congratulations! You have successfully installed Kuma on Kubernetes 🚀.

    In order to start using Kuma, it's time to check out the quickstart guide for Kubernetes deployments.

    # Argo CD

    Kuma requires a certificate to verify a connection between the control plane and a data plane proxy. Kuma Helm chart autogenerate self-signed certificate if the certificate isn't explicitly set. Argo CD uses helm template to compare and apply Kubernetes YAMLs. Helm template doesn't work with chart logic to verify if the certificate is present. This results in replacing the certificate on each Argo redeployment. The solution to this problem is to explicitly set the certificates. See "Data plane proxy to control plane communication" to learn how to preconfigure Kuma with certificates.

    Last Updated: 8/22/2022, 3:23:49 PM