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
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.
The text was updated successfully, but these errors were encountered:
k8s-ci-robot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Sep 8, 2024
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.
The text was updated successfully, but these errors were encountered: