This chart bootstraps all of Dapr Operator components on a Kubernetes cluster using the Helm package manager.

This chart installs multiple Dapr components via "child-charts":

• Dapr Component and Configuration Kubernetes CRDs
• Dapr RBAC components
  • Cluster Role Binding
  • Service Account
• Dapr Operator
• Dapr Placement

• Kubernetes 1.9 or newer cluster with RBAC (Role-Based Access Control) enabled is required
• Helm 2.14 or newer or alternately the ability to modify RBAC rules is also required

1. If a service account has not already been installed for Tiller, install one:

   $ kubectl apply -f https://github.com/Azure/helm-charts/blob/master/docs/prerequisities/helm-rbac-config.yaml
   

2. Install Tiller on your cluster with the service account:

   $ helm init --service-account tiller --history-max 200
   

The chart deploys pods that consume minimum resources as specified in the resources configuration parameter.

Make sure helm is initialized in your running kubernetes cluster.

For more details on initializing helm, Go here

1. Add Azure Container Registry as an helm repo

   helm repo add dapr https://daprio.azurecr.io/helm/v1/repo
   helm repo update
   

2. Install the Dapr chart on your cluster in the dapr-system namespace:

   helm install dapr/dapr --name dapr --namespace dapr-system
   

Once the chart installation is done, verify the Dapr operator pods are running in the dapr-system namespace:

kubectl get pods --namespace dapr-system

To uninstall/delete the dapr release but continue to track the release:

helm delete dapr

To uninstall/delete the dapr release completely and make its name free for later use:

helm delete --purge dapr