Skip to content
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

Support csi.storage.k8s.io/fstype key in StorageClass parameters #598

Closed
tksm opened this issue Jul 2, 2021 · 1 comment
Closed

Support csi.storage.k8s.io/fstype key in StorageClass parameters #598

tksm opened this issue Jul 2, 2021 · 1 comment

Comments

@tksm
Copy link

tksm commented Jul 2, 2021

Describe the solution you'd like

I would like to use csi.storage.k8s.io/fstype key instead of fsType in StorageClass parameters since fsType key has been deprecated since csi-provisioner v1.0.1.

It seems that the current Trident (v21.04.1) does not allow unexpected parameters in StorageClass. When I set csi.storage.k8s.io/fstype in StorageClass, I get the following error in the Trident log.

time="2021-07-02T06:52:18Z" level=error msg="K8S helper could not process the storage class attribute csi.storage.k8s.io/fstype" error="unrecognized storage attribute: csi.storage.k8s.io/fstype" name=ontap-block parameters="map[backendType:ontap-san csi.storage.k8s.io/fstype:ext4]" provisioner=csi.trident.netapp.io requestID=8fbfe6cb-fe57-43fd-9604-62960c51daf2 requestSource=Kubernetes

Additional context

I set fsType for fixing #454 (comment) .

@gnarl
Copy link
Contributor

gnarl commented Feb 17, 2022

This enhancement request is addressed with commit e9901c2 and will be included in the Trident v22.04 release.

@gnarl gnarl closed this as completed Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants