Open McMac opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Trying to use nfs-ganesha as local RWM storage on Windows 11 + WSL2 + Docker Desktop + Kubernetes.
Using this as values.yaml
and then launching via
helm install nfs-server-provisioner nfs-ganesha-server-and-external-provisioner/nfs-server-provisioner -f storage/values.yaml
Testing this with a local Jenkins pipeline, the runtime goes from roughly a minute up to 19 minutes!
Am I doing something wrong? Are the given parameters incomplete? The exact same config works on Mac + Docker Desktop so I am assuming it is related to WSL2/Win somehow.
Any workarounds? Suggestions? Any updates necessary to nfs ganesha? Parameters? Different default hostpath? Or update to the documentation?