CSI and Local Volume

[nevermore-muyi]

Hi, it's there any plans for csi and local volume? Just as the follow talks:
kubernetes-retired/external-storage#824
thanks.
@cofyc @pohly

[pohly]

Quite a bit is going on regarding that:

• provisioning: deployment without central controller #487
• storage capacity: https://github.com/orgs/kubernetes-csi/projects/32
• inline, ephemeral volumes: https://github.com/orgs/kubernetes-csi/projects/34

[nevermore-muyi]

@pohly maybe we can use the idea from topolvm,use a crd for proxy, provisioner and csi driver interact with the crd.
Just as the blog describes: https://blog.kintone.io/entry/topolvm.

[pohly]

I'm familiar with TopoLVM. I think the extension that I am planning for external-provisioner will be simpler (no need for extra CRDs, less code).

[nevermore-muyi]

@pohly Excuse me and can you describe the next step plan about this?
Is the plan like this?

1. external-provisioner deploy on each node
2. use storage capacity for volume dynamic provisioning

[nevermore-muyi]

And which release version (kubernetes and csi) we can see the new feature?

[pohly]

That's indeed the plan.

Deploying external-provisioner on each node is meant to go into the next external-provisioner release for Kubernetes 1.20.

Storage capacity tracking remains as alpha in 1.20. I hope to get it to beta in 1.21.

[nevermore-muyi]

@pohly thank you, look forward to the new feature.

[nevermore-muyi]

@pohly Except external-provisioner, resizing and snapshot are also need considered in the future.

[pohly]

I only plan to work on external-provisioner. Someone else will have to look into resizing and snapshotting.

[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

[pohly]

For the other components:

• distributed snapshotting external-snapshotter#484
• distributed resizing external-resizer#142

For external-provisioner we are done.

/close

[k8s-ci-robot]

@pohly: Closing this issue.

In response to this:

For the other components:

• distributed snapshotting external-snapshotter#484
• distributed resizing external-resizer#142

For external-provisioner we are done.

/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.