Open luanshuo opened 4 months ago
666
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
In our cluster,we have two nfs server,so we create two provisioner example: nfs-a, nfs-b nfs-b was recently created.
after create nfs-two provisioner,we create some new pvc(nfs5、nfs6、nfs7、nfs8),but long time was no success.
We ran the command "kubectl get pvc" to check the status of the PVC.
check provisioner log
Then, in our tests, creating new files and directories and performing read and write operations successfully. create new file/dir all action was success, read or write was success too
After restarting the pod, all PVCs were successfully created.