Skip to content
This repository has been archived by the owner on Oct 21, 2020. It is now read-only.

nfs-client: missing namespace for RoleBinding #1278

Closed
curx opened this issue Feb 7, 2020 · 0 comments
Closed

nfs-client: missing namespace for RoleBinding #1278

curx opened this issue Feb 7, 2020 · 0 comments

Comments

@curx
Copy link
Contributor

curx commented 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:

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"
...
curx added a commit to curx/external-storage that referenced this issue Feb 7, 2020
@curx curx closed this as completed Feb 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant