Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request]: Publish CSI driver also for Docker Swarm #408

Closed
olljanat opened this issue Feb 5, 2023 · 4 comments
Closed

[Feature request]: Publish CSI driver also for Docker Swarm #408

olljanat opened this issue Feb 5, 2023 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@olljanat
Copy link

olljanat commented Feb 5, 2023

Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
Recently published Docker 23.0.0 added CSI support for Swarm mode so it is possible to use this CSI driver with it but it need to be packaged as Docker plugin.

I have build some example scripts and guidance to https://github.com/olljanat/csi-plugins-for-docker-swarm and there is fully working example for csi-driver-nfs too.

Describe alternatives you've considered

Additional context

@Syntax3rror404
Copy link

Docker Swarm != kubernetes

@olljanat
Copy link
Author

Container Storage Interface (CSI) is standard. Kubernetes just happens to be first one who implemented it. Nomad was second and now also Docker Swarm have support for it.

@kfox1111
Copy link

I don't think its an unreasonable feature, but the current maintainers are the kubernetes-csi team. They have lots on their plate already. @olljanat if you prepared a pr against this repo and stepped up to maintain it, its much more likely to get in?

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants