You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to manually create persistent volumes in order to get this example to work. Is that expected, or is there likely something wrong with my configuration of minikube?
If it's expected that the user should manually create the persistent volumes, I'd be happy to update the instructions and share my example. Here's what I did:
@blachniet how did you tie back the PVs to the stateful set? Since even after creating the PVs I am getting the same error as before i.e.
SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "data-consul-0", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "data-consul-0", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "data-consul-0", which is unexpected.`
I don't think that there was anything else I needed to do in order to tie the stateful set to the PVs. The persistent volumne claims in the stateful set should match to the PVs created by this configuration.
@blachniet yes, I met this problem as well, and manually created 3 PVs to make it work
@tankchintan agree with @blachniet , PVC will automatically select from the PV pools (make sure you have 3 available, also I don't set storageClassName: default
I had to manually create persistent volumes in order to get this example to work. Is that expected, or is there likely something wrong with my configuration of minikube?
If it's expected that the user should manually create the persistent volumes, I'd be happy to update the instructions and share my example. Here's what I did:
The text was updated successfully, but these errors were encountered: