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
{{ message }}
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.
Each cluster may have different CSI provisioners so the storageClassName should be a configurable variable.
In fact, usually it shouldn't need to be set because the cluster's default storageClass should be sufficient. I think a PVC should only need to specify a storageClass if there are multiple types of storage available and it has a strong opinion on which type of storage it wants, so having storageClassName absent (unless defined by the user) may be a suitable default.
https://github.com/slateci/slate-catalog/blob/master/stable/osg-frontier-squid/osg-frontier-squid/templates/pvc.yaml#L17
Each cluster may have different CSI provisioners so the storageClassName should be a configurable variable.
In fact, usually it shouldn't need to be set because the cluster's default storageClass should be sufficient. I think a PVC should only need to specify a storageClass if there are multiple types of storage available and it has a strong opinion on which type of storage it wants, so having storageClassName absent (unless defined by the user) may be a suitable default.
Note that the DefaultStorageClass admission controller is enabled by default.
Moreover, to support the use of statically provisioned volumes, it would be good for the helm chart to also support setting
volumeName
, withstorageClassName: ""
as described here:https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reserving-a-persistentvolume
NB
storageClassName: ""
is different from not having a storageClassName.The text was updated successfully, but these errors were encountered: