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

Possibility to configure pvDir for storage-provisioner addon #8903

Closed
g9rga opened this issue Aug 2, 2020 · 3 comments
Closed

Possibility to configure pvDir for storage-provisioner addon #8903

g9rga opened this issue Aug 2, 2020 · 3 comments
Labels
addon/storage-provisioner Issues relating to storage provisioner addon co/docker-driver Issues related to kubernetes in container kind/feature Categorizes issue or PR as related to a new feature. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@g9rga
Copy link

g9rga commented Aug 2, 2020

I have a huge minikube cluster for local development with many stateful services(like mysql, rabbitmq, etc).
If I use docker driver in case of minikube profile recreation(for example, upgrading k8s version or changing cluster resources or something else) I will lose all of my persistent data, because in current implementation pvDir is a constant - /tmp/hostpath-provisioner.

It would be nice to have possibility to configure pvDir option for storage-provisioner, like: minikube addons configure storage-provisioner, then I could set pvDir to host mounted directory, create necessary pv on cluster setup and all my persistent data would be available on profile recreation.

What do you think about it?

P.S. Now, I use my own version of storage-provisoner to protect my data from losing.

@afbjorklund afbjorklund added the addon/storage-provisioner Issues relating to storage provisioner addon label Aug 5, 2020
@afbjorklund
Copy link
Collaborator

Seems like a duplicate of #3318 and #5144, but I guess it is more about #8151 - it was never supposed to use /tmp

In the current implementation of minikube (docker driver), the persistent volumes are now being stored on /var instead.

There's another story about host mounts: #7604

I guess those could be mounted in /tmp (or /var)

@afbjorklund afbjorklund added co/docker-driver Issues related to kubernetes in container kind/feature Categorizes issue or PR as related to a new feature. labels Aug 5, 2020
@afbjorklund afbjorklund changed the title [Feature request] Possibility to configure pvDir for storage-provisioner addon Possibility to configure pvDir for storage-provisioner addon Aug 5, 2020
@afbjorklund afbjorklund added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Aug 5, 2020
@g9rga g9rga closed this as completed Aug 5, 2020
@g9rga
Copy link
Author

g9rga commented Aug 5, 2020

@afbjorklund ok, I understood, thank you so much for reply

@afbjorklund
Copy link
Collaborator

@g9rga : no worries, sorry about the data loss. But with minikube 1.12.2, they should end up on the docker volume

One current "problem" with minikube is that both container images and persistent data is mixed, on the same disk image

If you have huge amounts of data, like your stateful services, then it might need dedicated disk images / docker volumes.

But the current design only allows for one /mnt/sda1 or /var, and there is no easy way to add custom images/volumes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addon/storage-provisioner Issues relating to storage provisioner addon co/docker-driver Issues related to kubernetes in container kind/feature Categorizes issue or PR as related to a new feature. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

2 participants