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
What happened:
When creating a StorageClass, if one use labels of a PVC or PV in the subDir, it is not correctely interpreted.
What you expected to happen:
I expect the NFS CSI storage class to create a folder hierarchy in the NFS server, using the label foo from my pvc.
Instead, I got something like:
i.e. that the labels are not correctly interpreted.
How to reproduce it:
Define a StorageClass in which you configured subDir with something like: subDir: ${pvc.metadata.namespace}/${pvc.metadata.labels.foo}/${pvc.metadata.name}
What happened:
When creating a StorageClass, if one use labels of a PVC or PV in the
subDir
, it is not correctely interpreted.What you expected to happen:
I expect the NFS CSI storage class to create a folder hierarchy in the NFS server, using the label
foo
from my pvc.Instead, I got something like:
i.e. that the labels are not correctly interpreted.
How to reproduce it:
Define a StorageClass in which you configured
subDir
with something like:subDir: ${pvc.metadata.namespace}/${pvc.metadata.labels.foo}/${pvc.metadata.name}
And then create a PVC with:
Create a pod using that PVC, and check which folder hierarchy it creates in the NFS
Environment:
registry.k8s.io/sig-storage/nfsplugin:v4.9.0
kubectl version
):Ubuntu 22.04.5 LTS
uname -a
):Linux 6.8.0-48-generic #48~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 7 11:24:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: