Hello Kubernetes tutorial should use the Helm installation instead of the dapr init -k approach

[salaboy]

Looking at this tutorial: https://github.com/dapr/quickstarts/tree/master/tutorials/hello-kubernetes , as a Kubernetes user I get scared of using a new CLI to install tools. I recommend switching to installing Dapr using Helm, a mechanism much more familiar to Kubernetes user.

This means changing dapr init -k --dev for the following commands:

Install Dapr

helm repo add dapr https://dapr.github.io/helm-charts/
helm repo update
helm upgrade --install dapr dapr/dapr \
--version=1.13.2 \
--namespace dapr-system \
--create-namespace \
--wait

To install Redis:

helm install redis oci://registry-1.docker.io/bitnamicharts/redis --version 17.11.3 --set "architecture=standalone" --set "master.persistence.size=1Gi"

If dapr init -k --dev is installing more things, for Kubernetes audience we need to make them explicit. Nobody likes installing things on a cluster without knowing exactly what is going on, it makes it more difficult to troubleshoot.

[pdebruin]

I agree that there should be a transparent description of how to deploy Dapr and friends to Kubernetes instead of --dev: Source: https://github.com/dapr/cli/blob/master/pkg/kubernetes/kubernetes.go#L99

• Redis https://github.com/dapr/docs/issues/3985#issuecomment-2171141011
• Zipkin https://docs.dapr.io/operations/observability/tracing/zipkin/
• Statestore & pubsub https://docs.dapr.io/getting-started/tutorials/configure-state-pubsub/ This way, cluster operators can understand what happens, and choose what and where they want to deploy.

[salaboy]

@pdebruin do you want to work with me on these changes ? I am happy to do a simple configuration first but I might need help for more advanced use cases

[joebowbeer]

Redis should be installed with a dedicated release name, which is currently dapr-dev-redis in default namespace. (Same applies to zipkin.)

helm install redis oci://registry-1.docker.io/bitnamicharts/redis --version 17.11.3 --set "architecture=standalone" --set "master.persistence.size=1Gi"

Consider using subcharts (umbrella) to make this even easier. Provide one dapr-dev umbrella chart, with redis and zipkin subcharts, and one dapr (non-dev) chart?