What would you like to be added:
We would like KIND to create a working storageclass by default.
Why is this needed:
We build a few Kubernetes operators. We would like to update our documentation so that users use KIND instead of Minikube as a test/dev Kubernetes setup in case they don't have one. Here is an example: https://github.com/stashed/docs/pull/54
One of the blockers for us is that KIND does not come with a working storageclass. We had success with Rancher's local provisioner. This is what we do internally. https://github.com/appscodelabs/e2e-test-setup/blob/kind-v0.6.1/run.sh
Obviously we could point our users to our custom docs for how to setup KIND, but it will be nice it KIND could ship a working storageclass solution.
This is the dynamic volume provisioning issue.
We're revisiting it this week.
On Sun, Dec 8, 2019, 13:19 Tamal Saha notifications@github.com wrote:
What would you like to be added:
We would like KIND to create a working storageclass by default.
Why is this needed:
We build a few Kubernetes operators. We would like to update our
documentation so that users use KIND instead of Minikube as a test/dev
Kubernetes setup in case they don't have one. Here is an example:
stashed/docs#54 https://github.com/stashed/docs/pull/54One of the blockers for us is that KIND does not come with a working
storageclass. We had success with Rancher's local provisioner. This is what
we do internally. https://github.com/appscodelabs/e2e-test-setupObviously we could point our users to our custom docs for how to setup
KIND, but it will be nice it KIND could ship a working storageclass
solution.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/1151?email_source=notifications&email_token=AAHADK76VZPZRQMFXOBBYUDQXVQF5A5CNFSM4JYASXYKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H65MYNQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADK5MSBFGI24IEAJBZ5LQXVQF5ANCNFSM4JYASXYA
.
Cool! Here is the script we are using now (also updated in the original post): https://github.com/appscodelabs/e2e-test-setup/blob/kind-v0.6.1/run.sh
Hi @tamalsaha, just wondering why couldn't you use default sc that ships with k8s ? It works fine with Kind on local host.
I don't remember it now. But we were creating a 3 node cluster and using dynamic provisioning. Something there did not work. If the default/built-in storageclass works, then that is even better.
the built in one (installed by kind) from k8s.io/hostpath built in driver has a few issues, namely that it requires containers to have UID=0, because it's based on the hostPath: ... driver for which it would be a violation of the security model to support non-root so upstream k8s does not respect fsgroup
this one alone is a big problem.
this, host restarts, user defined networks, and registries are on my near term list, in that order, other than ongoing maintenance stuff etc...
/assign
/lifecycle active
Most helpful comment
the built in one (installed by kind) from k8s.io/hostpath built in driver has a few issues, namely that it requires containers to have UID=0, because it's based on the
hostPath: ...driver for which it would be a violation of the security model to support non-root so upstream k8s does not respect fsgroupthis one alone is a big problem.
this, host restarts, user defined networks, and registries are on my near term list, in that order, other than ongoing maintenance stuff etc...