minikube: latest storage-provisioner: cannot get resource "endpoints" in API group "" in the namespace "kube-system"

Not sure, but it seems related to https://github.com/kubernetes/minikube/pull/6511/files

The exact command to reproduce the issue:

minikube start
kubectl create namespace test
kubectl apply -f pvc.yaml

The full output of the command that failed:

storage provisioner logs:

E0206 10:46:39.353949       1 leaderelection.go:331] error retrieving resource lock kube-system/k8s.io-minikube-hostpath: endpoints "k8s.io-minikube-hostpath" is forbidden: User "system:serviceaccount:kube-system:storage-provisioner" cannot get resource "endpoints" in API group "" in the namespace "kube-system

The output of the minikube logs command:

The operating system version:

minikube version
minikube version: v1.5.2
commit: 792dbf92a1de583fcee76f8791cff12e0c9440ad-dirty

cat /etc/os-release 
NAME="Linux Mint"
VERSION="19.3 (Tricia)"

pvc.yaml:

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test
  namespace: test
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 7
Comments: 20 (8 by maintainers)

Most upvoted comments

Likely related to #6496

Since the bug is affecting older versions, it sounds like we rolled out a buggy provisioner image. I’ll see if I can back it out. In the future we need to make sure to not repush to specific revisions.

tstromberg on Feb 6, 2020

@dimara thanks for the hashes!

I ran:

docker tag gcr.io/k8s-minikube/storage-provisioner@sha256:088daa9fcbccf04c3f415d77d5a6360d2803922190b675cb7fc88a9d2d91985a gcr.io/k8s-minikube/storage-provisioner:v1.8.1
docker push gcr.io/k8s-minikube/storage-provisioner:v1.8.1

Please let me know if this has helped in your environment.

tstromberg on Feb 6, 2020

I was broken by this for a while before I figured out that in order to fix I have to completely purge my ~/.minikube directory so that it will fetch the corrected v1.8.1. Would it be good to publish a v1.8.2 so that anyone who already has the broken v1.8.1 image gets the update?

djmarcin on Feb 12, 2020

I see that PR #6156 changes the storage-provisioner code. @tstromberg @nanikjava shouldn’t the STORAGE_PROVISIONER_TAG variable be changed after this?

dimara on Feb 6, 2020