PVC stay "pending", storage provisioner is failing to list #8414
Comments
ctron
changed the title
|
Taking a closer look, this is some weird "fails to list" issue, rather than a permission issue. |
medyagh
added
the
addon/storage-provisioner
|
@ctron I am curious, could you share the steps to create the PVC so I could replicate this issue myself? if this is a permission issue, do you mind trying with |
medyagh
added
triage/needs-information
|
It looks like the storage-provisioner image ( If I change the image to |
|
Related: #6523 |
priyawadhwa
removed
the
triage/needs-information
That worked for me, in particular, the following commands fixed the issue on minikube 1.12.1 #minikube delete
docker pull gcr.io/k8s-minikube/storage-provisioner:latest
docker tag gcr.io/k8s-minikube/storage-provisioner:latest gcr.io/k8s-minikube/storage-provisioner:v1.8.1
minikube start
# Taken from: https://github.com/kubernetes/minikube/blob/e5cfa386b1d978096d3e8d917f5ed07b960a457c/deploy/addons/storage-provisioner/storage-provisioner.yaml.tmpl
cat <<EOF | kubectl apply -f -
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: system::leader-locking-storage-provisioner
namespace: kube-system
labels:
addonmanager.kubernetes.io/mode: EnsureExists
rules:
- apiGroups:
- ""
resources:
- endpoints
verbs:
- watch
- apiGroups:
- ""
resourceNames:
- k8s.io-minikube-hostpath
resources:
- endpoints
verbs:
- get
- update
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: leader-locking-storage-provisioner
namespace: kube-system
labels:
addonmanager.kubernetes.io/mode: EnsureExists
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: system::leader-locking-storage-provisioner
subjects:
- kind: ServiceAccount
name: storage-provisioner
namespace: kube-system
---
apiVersion: v1
kind: Endpoints
metadata:
name: k8s.io-minikube-hostpath
namespace: kube-system
labels:
addonmanager.kubernetes.io/mode: Reconcile
EOF |
|
Hey @ctron in the past few months we've upgraded the storage provisioner and fixed some bugs. Could you try:
Thanks. |
priyawadhwa
added
the
triage/needs-information
Will do. |
|
@ctron - any update? We're now on minikube v1.4.0 -- though I don't think the storage provisioner has changed since v1.13.1. |
|
@ctron do you still have this issue with latest version of minikube? |
|
I am now on |
|
I just checked, looks like |
|
Thanks for the update! |
Steps to reproduce the issue:
minikube start --cpus 4 --memory 8192Full output of failed command:
Full output of
minikube startcommand used, if not already included:Logs of the storage provisioner:
Optional: Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: