public_git
/
democratic-csi
mirror of https://github.com/democratic-csi/democratic-csi.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

.

This commit is contained in:
D1StrX 2021-12-24 19:44:34 +01:00
parent 1ddc7958af
commit 7cce02c53f
1 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -3,14 +3,10 @@
# Introduction # Introduction
## What is Democratic-CSI? ## What is Democratic-CSI?
`Democratic-CSI` implements the `csi` (Container Storage Interface) specifications `Democratic-CSI` implements the `csi` (Container Storage Interface) specifications providing storage for various container orchestration systems (*ie: Kubernetes, Nomad, OpenShift*).
providing storage for various container orchestration systems (*ie: Kubernetes, Nomad, OpenShift*).
The current focus is providing storage via iSCSI or NFS from ZFS-based storage The current *focus* is providing storage via iSCSI or NFS from ZFS-based storage systems, predominantly `TrueNAS / FreeNAS` and `ZoL on Ubuntu`.
systems, predominantly `TrueNAS / FreeNAS` and `ZoL on Ubuntu`. The current *drivers* implement the depth and breadth of the `csi` specifications, so you have access to resizing, snapshots, clones, etc functionality.
The current drivers implement the depth and breadth of the `csi` specifications, so you
have access to resizing, snapshots, clones, etc functionality.
## What can Democratic-CSI offer? ## What can Democratic-CSI offer?
**Several implementations of `CSI` drivers** **Several implementations of `CSI` drivers**
@ -137,9 +133,7 @@ Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Param
### **ZFS-local-ephemeral-inline** ### **ZFS-local-ephemeral-inline**
This `driver` provisions node-local ephemeral storage on a per-pod basis. Each This `driver` provisions node-local ephemeral storage on a per-pod basis. Each node should have an identically named ZFS pool created and avaialble to the `driver`.
node should have an identically named ZFS pool created and avaialble to the
`driver`.
*NOTE:* This is *NOT* the same thing as using the docker ZFS storage *NOTE:* This is *NOT* the same thing as using the docker ZFS storage
driver (although the same pool could be used). No other requirements are driver (although the same pool could be used). No other requirements are
necessary. More regarding to this can be found here: [Pod Inline Volume Support](https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html) necessary. More regarding to this can be found here: [Pod Inline Volume Support](https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html)