bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
8.65k stars 9.01k forks source link

PVC not working on Minikube 0.9.0 #131

Closed migmartri closed 7 years ago

migmartri commented 7 years ago

Trying to run the Redmine chart which comes with persistence enabled by default I get:


kubectl get pods
NAME                                   READY     STATUS    RESTARTS   AGE
giddy-skunk-mariadb-4195510591-cwdid   0/1       Pending   0          31s
giddy-skunk-redmine-3930201193-68jv7   0/1       Pending   0          31s
migmartri ~/work/bitnami/charts/redmine master $ kubectl get pvc
NAME                  STATUS    VOLUME    CAPACITY   ACCESSMODES   AGE
giddy-skunk-mariadb   Pending                                      3m
giddy-skunk-redmine   Pending                                      3m

Provisioner plugin not found.

migmartri ~/work/bitnami/charts/redmine master $ kubectl describe pvc giddy-skunk-mariadb
Name:       giddy-skunk-mariadb
Namespace:  default
Status:     Pending
Volume:     
Labels:     <none>
Capacity:   
Access Modes:   
Events:
  FirstSeen LastSeen    Count   From                SubobjectPath   Type        Reason          Message
  --------- --------    -----   ----                -------------   --------    ------          -------
  3m        11s     16  {persistentvolume-controller }          Warning     ProvisioningFailed  No provisioner plugin found for the claim!

And this is the error message shown in the Pod

kubectl describe pods giddy-skunk-redmine-3930201193-68jv7
Name:       giddy-skunk-redmine-3930201193-68jv7
Namespace:  default
Node:       /
Labels:     app=giddy-skunk-redmine
        chart=redmine-redmine
        heritage=Tiller
        pod-template-hash=3930201193
        release=giddy-skunk
Status:     Pending
IP:     
Controllers:    ReplicaSet/giddy-skunk-redmine-3930201193
Containers:
  giddy-skunk-redmine:
    Image:  bitnami/redmine:3.3.0-r2
...
...
Events:
  FirstSeen LastSeen    Count   From            SubobjectPath   Type        Reason          Message
  --------- --------    -----   ----            -------------   --------    ------          -------
  6m        55s     22  {default-scheduler }            Warning     FailedScheduling    PersistentVolumeClaim is not bound: "giddy-skunk-redmine"

Using Minikube 0.9.0 in a brand new VM and cluster.

minikube version
minikube version: v0.9.0
migmartri commented 7 years ago

cc @prydonius

prydonius commented 7 years ago

Turns out it was added in 0.10.0 according to the changelog (https://github.com/kubernetes/minikube/blob/master/CHANGELOG.md#version-0100---9152016). Can you try that?

prydonius commented 7 years ago

I can confirm my PVCs got dynamically bound on 0.10.0.

migmartri commented 7 years ago

Yes, it works for me in 0.10.0

Thanks.