Open RyanLettieri opened 2 years ago
@RyanLettieri Will you pick up this issue?
We should have a valid automation for ARM64 too.
Per #791 I'd like to understand who needs this [i.e. arm64 on the server support for Dapr] and why. It's a fairly heavy lift, and I've seen no hard asks. @artursouza @msfussell
@artursouza - Can we close this issue?
Has this been fixed? M1 Mac has ARM64 architecture, so this is a way to make sure QuickStarts work on those.
We actually test Mac M1/apple silicon as a part of quickstarts release. This particular test has never in my knowledge helped us find issues for Mac's ARM. Also this goes steps further to be a linux arm + k8s scenario. I just don't see this as a priority. if you'd like to contribute it, that's cool.
Close this?
dapr init -k --dev
installs bitnami/redis - https://github.com/dapr/cli/pull/1333
and arm64 was added to bitnami/redis - https://github.com/bitnami/charts/issues/7305
Expected Behavior
There are multiple issues with the tutorials:
Actual Behavior
A failed run occurs when running any of the tutorials that require a redis statestore due to the fact that redis is not started when dapr is deployed to a kubernetes cluster.
Steps to Reproduce the Problem
Problem 1: Redis not being deployed in the cluster
sudo dockerd
minikube start
)dapr init -k --runtime-version 1.9.0-rc.3
cd quickstarts/tutorials/hello-kubernetes; make validate
Problem 3: False status for "HEALTHY" on dapr
sudo dockerd
minikube start
)dapr init -k --runtime-version 1.9.0-rc.3
Here's a link on how to setup redis: https://docs.dapr.io/getting-started/tutorials/configure-state-pubsub/#step-1-create-a-redis-store