One would expect that by using kfp.kubernetes.CreatePVC without specifying storage_class_name results in using this default storage class. Instead, a hardcoded standard storage class is used (no matter if such class even exist on the cluster)
Environment
How did you deploy Kubeflow Pipelines (KFP)? - as part of Red Hat OpenShift AI
KFP version: 2.2.0
KFP SDK version: 2.10.1
Steps to reproduce
Use kfp.kubernetes.CreatePVC task without storage_class_name. A PVC with .spec.storageClassName: "standard" is created instead of one using the Storage class actually set as the default one in Kubernetes.
Expected result
Not specifying storage_class_name results in submitting the PVC without .spec.storageClassName property set and therefore result in the Kubernetes default storage class being applied.
Kubernetes has a concept of a default Storage Class.
One would expect that by using
kfp.kubernetes.CreatePVCwithout specifyingstorage_class_nameresults in using this default storage class. Instead, a hardcodedstandardstorage class is used (no matter if such class even exist on the cluster)Environment
Steps to reproduce
Use
kfp.kubernetes.CreatePVCtask withoutstorage_class_name. A PVC with.spec.storageClassName: "standard"is created instead of one using the Storage class actually set as the default one in Kubernetes.Expected result
Not specifying
storage_class_nameresults in submitting the PVC without.spec.storageClassNameproperty set and therefore result in the Kubernetes default storage class being applied.Materials and Reference
Impacted by this bug? Give it a 👍.