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
{{ message }}
This repository has been archived by the owner on Oct 21, 2020. It is now read-only.
if nfs-client is deployed via kubectl without helm and install in another namespace as default, the nfs-client will not be functional and at the logs will be filled with errors:
Reproduce:
kubectl create namespace nfs-client
sed -i'' "s/namespace:.*/namespace: nfs-client/g" ./deploy/rbac.yaml ./deploy/deployment.yaml
kubectl create -f deploy/rbac.yaml -f deploy/deployment.yaml
kubectl --namespace nfs-client logs -l app=nfs-client-provisioner
E0207 18:06:51.880561 1 leaderelection.go:234] error retrieving resource lock nfs-client/fuseim.pri-ifs: endpoints "fuseim.pri-ifs" is forbidden: User "system:serviceaccount:nfs-client:nfs-client-provisioner" cannot get resource "endpoints" in API group "" in the namespace "nfs-client"
E0207 18:06:55.236994 1 leaderelection.go:234] error retrieving resource lock nfs-client/fuseim.pri-ifs: endpoints "fuseim.pri-ifs" is forbidden: User "system:serviceaccount:nfs-client:nfs-client-provisioner" cannot get resource "endpoints" in API group "" in the namespace "nfs-client"
...
The text was updated successfully, but these errors were encountered:
curx
added a commit
to curx/external-storage
that referenced
this issue
Feb 7, 2020
if nfs-client is deployed via kubectl without helm and install in another namespace as default, the nfs-client will not be functional and at the logs will be filled with errors:
Reproduce:
The text was updated successfully, but these errors were encountered: