technofab/zfs-localpv
1
0
Fork 0
mirror of https://github.com/TECHNOFAB11/zfs-localpv.git synced 2025-12-12 06:20:11 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
251 commits 1 branch 0 tags 33 MiB
Commit graph

7 commits

Author SHA1 Message Date
Suraj Deshmukh
273bf148d4
chore(yaml): fix bunch of typos (#348) 
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
 2021-06-24 18:39:26 +05:30
Pawan Prakash Sharma
8cc56377bd
chore(yaml): fixing autogen yaml description (#301) 
Signed-off-by: Pawan <pawan@mayadata.io>
 2021-04-01 13:02:51 +05:30
Shubham Bajpai
533e17a9aa
chore(k8s): updated storage and apiextension version to v1 (#299) 
Signed-off-by: shubham <shubham.bajpai@mayadata.io>
 2021-03-31 15:09:48 +05:30
vaniisgh
8bbf3d7d2f
feat(zfspv) Add golint check to travis (#175) 
Signed-off-by: vaniisgh <vanisingh@live.co.uk>
 2020-07-07 18:21:02 +05:30
Pawan
27065bf40a feat(shared): adding shared mount support ZFSPV volumes 
Applications who want to share a volume can use below storageclass
to make their volumes shared by multiple pods

```yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: openebs-zfspv
parameters:
  shared: "yes"
  fstype: "zfs"
  poolname: "zfspv-pool"
provisioner: zfs.csi.openebs.io
```

Now the provisioned volume using this storageclass can be used by multiple pods.
Here pods have to make sure of the data consistency and have to have locking mechanism.
One thing to note here is pods will be scheduled to the node where volume is present
so that all the pods can use the same volume as they can access it locally only.
This was we can avoid the NFS overhead and can get the optimal performance also.

Also fixed the log formatting in the GRPC log.

Signed-off-by: Pawan <pawan@mayadata.io>
 2020-07-02 00:40:15 +05:30
Pawan
472fd603ac feat(beta): adding v1 CRD for ZFS-LocalPV 
Moving the CRDs to stable v1 version.

Signed-off-by: Pawan <pawan@mayadata.io>
 2020-06-04 16:02:32 +05:30
Pawan Prakash Sharma
ae724ee096
feat(validation): adding validation for ZFSPV CR parameters (#66) 
Validating few parameters for the ZFSVolume custom resource

- compression can be "on", "off", "lzjb", "gzip", "gzip-[1-9]", "zle" and "lz4"
- encryption can be "on", "off", "aes-128-ccm", "aes-192-ccm", "aes-256-ccm", "aes-128-gcm", "aes-192-gcm", and "aes-256-gcm"
- dedup can be "on" and "off"
- poolname can be string
- ownernodeid can be string
- thinprovision can be "yes" and "no"
- volumetype can be "DATASET" and "ZVOL"

Also added required fields needed to create ZFSVolume CR
- ownerNodeID
- poolname
- volumeType
- capacity


Signed-off-by: Pawan <pawan@mayadata.io>
 2020-04-14 17:26:46 +05:30