kubernetes/minikube

Creation of additional storage classes with dynamic volume provisioning: impossible or documentation lacking?

Open

#11,947 opened on Jul 9, 2021

View on GitHub
 (27 comments) (2 reactions) (0 assignees)Go (5,222 forks)batch import
addon/storage-provisionerhelp wantedkind/featurelifecycle/stalepriority/backlog

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate if minikube supports creating additional storage classes with dynamic provisioning via custom manifests or addons. If not, explore the feasibility of adding such support.
Tech stack
go
Domain
backendinfrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Kuberneteskubectl
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60