Is it possible to add custom plugin in csi provisioning flow?

kubernetes-csi / external-provisioner

Sidecar container that watches Kubernetes PersistentVolumeClaim objects and triggers CreateVolume/DeleteVolume against a CSI endpoint

Apache License 2.0

338 stars 327 forks source link

Is it possible to add custom plugin in csi provisioning flow? #570

Closed asifdxtreme closed 3 years ago

asifdxtreme commented 3 years ago

Usecase : A data management framework wants to add intelligence or tweak the provisioning before the external-provisioner sends the request to csi driver for provisioning of the pv/pvc.

Solution : ???

Suggestion :

Following the priniciples of extensible code, we can add the options of dynamic plugin which when enabled calls the custom bussiness code before the sending the request to csi driver for provisioning.
Provide a feature via arguments which when enabled calls the new sidecar(provided by framework) to do the business logic before provisioning over here

pohly commented 3 years ago

Other solutions:

fork the external-provisioner and implement your changes in the fork
implement a proxy which accepts gRPC calls on a Unix domain socket, acts on those it cares about (CreateVolume?) and then sends them on to the actual CSI driver: external-provisioner -> proxy -> CSI driver

msau42 commented 3 years ago

What kind of modifications do you want to make to the provisioning request? Can a mutating webhook address your use case? Or is this a use case for the data populator feature?

fejta-bot commented 3 years ago

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

k8s-triage-robot commented 3 years ago

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 commented 3 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen
Mark this issue or PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 3 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-csi/external-provisioner/issues/570#issuecomment-907561005): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.