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
Describe the bug
A clear and concise description of what the bug is.
there two nodes in cluster. kb-addon-csi-hostpath-driver is running on node02 , and pvc creating faile: no topology key found on CSINode k8s-node01
Warning ProvisioningFailed 46s (x10 over 9m17s) hostpath.csi.k8s.io_kb-addon-csi-hostpath-driver-0_3b3a7aae-0a37-4162-9134-1bdf49af7f43 failed to provision volume with StorageClass "csi-hostpath-sc": error generating accessibility requirements: no topology key found on CSINode k8s-node01
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
there two nodes in cluster. kb-addon-csi-hostpath-driver is running on node02 , and pvc creating faile: no topology key found on CSINode k8s-node01
Warning ProvisioningFailed 46s (x10 over 9m17s) hostpath.csi.k8s.io_kb-addon-csi-hostpath-driver-0_3b3a7aae-0a37-4162-9134-1bdf49af7f43 failed to provision volume with StorageClass "csi-hostpath-sc": error generating accessibility requirements: no topology key found on CSINode k8s-node01
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: