in statestore example: helm install redis bitnami/redis status always Pending
See original GitHub issueAsk your question here
in statestore example: helm install redis bitnami/redis status always Pending.
kubectl get pods:
redis-master-0 0/2 Pending 0 8m11s
redis-slave-0 0/2 Pending 0 8m11s
kubectl describe pods redis:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 74s (x5 over 5m43s) default-scheduler running "VolumeBinding" filter plugin for pod "redis-slave-0": pod has unbound immediate PersistentVolumeClaims
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Redis helm chart install - Resources in pending state
helm install my-release my-repo/redis -n demo. I see all resources are in pending state - "kubectl logs" against any object is blank.
Read more >Redis
To setup Redis state store create a component of type state.redis . See this guide on how to create and apply a state...
Read more >helm bitnami/redis does not provide peristent volume
1. Run kubectl get pvc. you should see the expected PVCs listed, but in Pending state. If you don't see that, this means...
Read more >How to deploy Redis in Kubernetes with Helm chart + Redis ...
1. Add the Helm repository containing the Redis chart you wish to install. I will use for this tutorial bitnami repo.
Read more >redis 17.15.6 · bitnami/bitnami
helm install my-release oci://registry-1.docker.io/bitnamicharts/redis. The command deploys Redis® on the Kubernetes cluster in the default configuration.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also, just for the sake of unblocking you, you should be able to disable persistence:
Try this and let me know if it unblocks you.
Note: Never do this in production, or you may suffer data loss
From this example, it looks like your redis instances are stuck in a terminating state. Running
kubectl describe pod redis-master-0
might give you more information on what went wrong.I’m going to close this issue, as running redis in a kubernetes cluster without persistent volume support is somewhat outside of the scope of the Dapr quickstarts. If you are still having trouble, could you please head on over to our community discord https://aka.ms/dapr-discord ? You’ll likely be able to get much faster response times there.