-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After the service nfs-server-provisioner is restarted, the following error will be reported: access denied by server while mounting #111
Comments
This happens in our setup too! |
You can fix the error by adding the following to the securityContext of the container: I will have a look at how we can patch this properly. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
I found out the deployment for the nfs server was not using persistence, that way, obviously, every restart would result in empty directory under Sorry for the mistake, but I'll let this comment here because someone could be missing persistence configuration too. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Hitting some of the same issues. Not sure what I'm missing for the ganesha specific nfs provisioner. It seems we are running it across multiple environments. Two of our environments are fine but the third environment seems to not be mounting. On the nfs side I did attempt to add the mountOptions detailed here: #34 After deleting the existing pvcs I'm thinking the change worked but having difficulty validating this part. I mainly want to confirm for the ganesha provisioner if I need the nfs-common and nfs-kernel-server packages installed. It seems we have nfs-common getting installed but can't find anywhere in the docs if these are required. If someone can confirm if those packages are required. Main issue is that pods are going down and not mounting to the existing pvcs. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
By default, persistence is set to Would it be possible to set it to |
No description provided.
The text was updated successfully, but these errors were encountered: