-
Notifications
You must be signed in to change notification settings - Fork 473
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
failed to provision volume with StorageClass "local-storage": configuration error, no node was specified #332
Comments
I have read something code about the errors, it seems there is no annotation of I have no ideas why and how to resolve it |
there is no # k get psp -A
Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
No resources found |
I have the same issue, and funny thing that yesterday it was working fine, and I did not change anything on my local k3s setup that uses this local-path provisioner. Edit:
to my pvc, or volumeClaimTemplates in the metadata section, it works. (where desktop-ad24a9m is my node) |
I guess it is because #296 updated |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Still happens in v0.0.30 when |
I confirm it still does to this day. |
Will investigate the issue soon |
Currently, I don't have too many thoughts for the issue. Any feedback or contribution is welcomed. Thanks. |
@derekbit I faced the same issue, below are the details and the workaround I applied (mentioned by captaingabi) Original code (this produces
once I hardcode the node name it begins to provision the PV properly
|
I have deployed local-path-privisioner with
v0.0.24
, when I apply a busybox to make a test, the pvc is always pending and reports errors aboutconfiguration error, no node was specified
.Here's my cluster info:
Something about the local-path-provisoner:
The text was updated successfully, but these errors were encountered: