Regis stuck Pending -- following "getting-started" tutorial

[EmmettPeck]

What happened?

I am following the "getting started" tutorial from the documentation, but getting-started-redis-managed-0 never makes it past pending, causing proxy nodes to fail on startup with the same error code as #250.

I am using the helm instructions from the installation page. I am having the same issue with v0.8.0 and v0.8.1. Regis is still pending after 30 minutes of following the steps up to cluster.yaml.

kubectl describe node <regis-node> yields:

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  2m33s (x4 over 17m)  default-scheduler  0/4 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.

Any help would be greatly appreciated. I would love the opportunity to work with this technology.

What components are involved in your issue?

Operator, Proxy API

Version

v0.8.1

Kubernetes Version

1.30.0

Relevant log output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[jeremylvln]

Hi @EmmettPeck,

It seems to be an issue with your cluster and not Shulker directly. pod has unbound immediate PersistentVolumeClaims means that your Kubernetes Cluster has not succeeded provisioning Redis's Volume. Can you take a look at the volume resource to see what is failing?

You can also test this simple tutorial from Kubernetes just to ensure your cluster can handle Volume s.

Get back to me when you'll have the results! Thanks!