Using in production

[tamalsaha]

Hello,
Is there any plans to make this a production quality driver? Or, this will remain as a non-production driver?

Thanks.

[pohly]

Is there any plans to make this a production quality driver?

No.

Is there a need for it? What would be the advantage over the in-tree emptydir or hostpath volume types?

I guess it could be used to manage additional disks, but that raises all kinds of questions that don't have good answers (IMHO).

[tamalsaha]

We want to use local volume for running databases. We have been using https://github.com/rancher/local-path-provisioner . But a CSI driver will be nice, since that is the future.

[aglitke]

I would also like to point this thread to https://github.com/kubevirt/hostpath-provisioner This driver sees significant usage and combined with @tamalsaha 's previous comment I think there is a case for a multi-node, production-grade driver. It would be nice if we could all work together on a single one instead of fragmenting. Hostpath is preferred over local-volume for several reasons including the possibility of dynamic provisioning. A CSI driver is superior because it is not deprecated technology and because CSI allows for snapshots and cloning.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.