Re: [kubernetes/kubernetes] Document how to write a new volume plugin (#13753)

[Saad Ali]

CC @kubernetes/sig-storage-misc

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[wyc]

This is my WIP:

https://github.com/wyc/k8s-community/blob/volume-guide/contributors/devel/developer-guides/volume-overview.md

Is this the right tone/scope/style?

[wyc]

Hey, I'm writing the FAQ section based on things that were confusing during writing the previous sections. I'm working on a question titled "How do cloud provider volume plugins figure out what mount device (e.g., /dev/sdc) a newly-attached volume will appear as?"

It seems that most of them query their respective APIs and are able to come up with some kind of block device mapping either directly or by something like LUN. What's the use of predicting the next available device?

https://github.com/kubernetes/kubernetes/blob/17e745631aa3af979628841d37bd42f27de3d2e8/pkg/cloudprovider/providers/aws/aws.go#L1223

https://github.com/kubernetes/kubernetes/blob/bf984aa328f3d3e5f8956f7d8e65c13c52102426/pkg/cloudprovider/providers/azure/azure_storage.go#L166

[wyc]

Okay a new look tells me that it's prevented here:

https://github.com/kubernetes/kubernetes/blob/17e745631aa3af979628841d37bd42f27de3d2e8/pkg/cloudprovider/providers/aws/aws.go#L1199

This will make it to the implementor's guide.

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[Qiming]

/remove-lifecycle stale
/lifecycle frozen

[David Zhu]

New plugins no longer being added/written. Please add new storage backends to Kubernetes through CSI: https://kubernetes-csi.github.io/docs/developing.html
/close

—
You are receiving this because you are on a team that was mentioned.

Reply to this email directly, view it on GitHub, or unsubscribe.

[Kubernetes Prow Robot]

Closed #13753.

[Kubernetes Prow Robot]

@davidz627: Closing this issue.

In response to this:

New plugins no longer being added/written. Please add new storage backends to Kubernetes through CSI: https://kubernetes-csi.github.io/docs/developing.html
/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.