vsphere-csi-driver icon indicating copy to clipboard operation
vsphere-csi-driver copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Support for Docker CSI volumes.

Open chrisbecke opened this issue 2 years ago • 10 comments

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug /kind feature

What happened:

Docker 23.0.0 is released with patch notes and includes support for CSI volumes via #41982.

Is there any intention to extend support for this?

chrisbecke avatar Feb 03 '23 12:02 chrisbecke

That would be very pleasing to have.

gabrielmocan avatar Feb 03 '23 13:02 gabrielmocan

Yes Docker 23.0.0 added CSI support for Swarm mode so unless this plugin uses Kubernetes specific implementation (works as controller, etc) it should be possible to make it working with Docker Swarm now.

However it still 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 which you might find useful.

olljanat avatar Feb 05 '23 10:02 olljanat

We have filed this request internally for review. I'll update this thread when I have more info.

adikul30 avatar Feb 10 '23 00:02 adikul30

there are some news?

turric4n avatar Jun 28 '23 06:06 turric4n

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-triage-robot avatar Jan 23 '24 12:01 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Feb 22 '24 12:02 k8s-triage-robot

push

turric4n avatar Feb 23 '24 18:02 turric4n

/remove-lifecycle rotten

divyenpatel avatar Mar 20 '24 18:03 divyenpatel