Creation of additional storage classes with dynamic volume provisioning: impossible or documentation lacking?
#11.947 aperta il 9 lug 2021
Metriche repository
- Star
- (31.799 stelle)
- Metriche merge PR
- (Merge medio 12g 19h) (43 PR mergiate in 30 g)
Descrizione
Running minikube version: v1.20.0, commit: c61663e942ec43b20e8e70839dcca52e44cd85ae
There is only one storage class created when starting a minikube:
$ kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
standard (default) k8s.io/minikube-hostpath Delete Immediate false 18h
Dynamic Provisioning in this storage class works fine.
I would like to add more storage classes with dynamic volume provisioning, so that I could test my PersistentVolumeClaim manifests (written for EKS) on Minikube without modifications. These storage classes need not be different physically or programmatically from the standard Minikube sc, but I need to test manifests for other clusters without modifications. Those manifests have different "storageClassName" attributes, like "gp3", "sc1" etc.
If the creation of additional storage classes with dynamic volume provisioning is possible, I cannot find it anywhere if it's documented for Minikube.