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
zfs-localpv/deploy/sample/zfspvcr.yaml

21 lines
401 B
YAML
Raw Normal View History

feat(zfspv): pvc should be bound only if volume has been created. The controller does not check whether the volume has been created or not and return successful. Which in turn binds the pvc to the pv. The PVC should not bound until corresponding zfs volume has been created. Now controller will check the ZFSVolume CR state to be "Ready" before returning successful. The CSI will retry the CreateVolume request when it will get a error reply and when the ZFS node agent creates the ZFS volume and sets the ZFSVolume CR state to be "Ready", the controller will return success for the CreateVolume Request and then PVC will be bound. Signed-off-by: Pawan <pawan@mayadata.io>
2020-05-18 16:30:20 +05:30
apiVersion: zfs.openebs.io/v1alpha1
fix(doc): updating sample ZFSVolume CR Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-08 15:00:35 +05:30
kind: ZFSVolume
feat(zfs-localpv): initial commit provisioning and deprovisioning of the volumes on the node where zfs pool has already been setup. Pool name and the volume parameters has to be given in storage class which will be used to provision the volume. Signed-off-by: Pawan <pawan@mayadata.io>
2019-09-12 12:32:17 +05:30
metadata:
fix(yaml): fixing mongo yaml As the selector is needed in the latest kubetnetes cluster Also updated zfs volume custom resource and renamed few fields of percona application. Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-23 20:06:43 +05:30
name: pvc-34133838-0d0d-11ea-96e3-42010a800114
fix(doc): updating sample ZFSVolume CR Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-08 15:00:35 +05:30
namespace: openebs
spec:
capacity: "4294967296"
compression: "off"
dedup: "off"
encryption: ""
fix(yaml): fixing mongo yaml As the selector is needed in the latest kubetnetes cluster Also updated zfs volume custom resource and renamed few fields of percona application. Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-23 20:06:43 +05:30
fsType: "zfs"
fix(doc): updating sample ZFSVolume CR Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-08 15:00:35 +05:30
keyformat: ""
keylocation: ""
ownerNodeID: zfspv-node1
poolName: zfspv-pool
feat(ZFSPV): adding support for applications to create "zfs" flesystem (#15) Application can now create a storageclass to create zfs filesystem apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: openebs-zfspv5 allowVolumeExpansion: true parameters: blocksize: "4k" fstype: "zfs" poolname: "zfspv-pool" provisioner: zfs.csi.openebs.io ZFSPV was supporting ext2/3/4 and xfs filesystem only which adds one extra filesystem layer on top of ZFS filesystem. So now we can driectly write to the ZFS filesystem and get the optimal performance by directly creating ZFS filesystem for storage. Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-21 19:00:15 +05:30
recordsize: 8k
fix(bug): fixed a typo for thinprovision json name. Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-08 16:19:12 +05:30
thinProvision: "off"
feat(ZFSPV): adding support for applications to create "zfs" flesystem (#15) Application can now create a storageclass to create zfs filesystem apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: openebs-zfspv5 allowVolumeExpansion: true parameters: blocksize: "4k" fstype: "zfs" poolname: "zfspv-pool" provisioner: zfs.csi.openebs.io ZFSPV was supporting ext2/3/4 and xfs filesystem only which adds one extra filesystem layer on top of ZFS filesystem. So now we can driectly write to the ZFS filesystem and get the optimal performance by directly creating ZFS filesystem for storage. Signed-off-by: Pawan <pawan@mayadata.io>
2019-11-21 19:00:15 +05:30
volumeType: DATASET
feat(zfspv): pvc should be bound only if volume has been created. The controller does not check whether the volume has been created or not and return successful. Which in turn binds the pvc to the pv. The PVC should not bound until corresponding zfs volume has been created. Now controller will check the ZFSVolume CR state to be "Ready" before returning successful. The CSI will retry the CreateVolume request when it will get a error reply and when the ZFS node agent creates the ZFS volume and sets the ZFSVolume CR state to be "Ready", the controller will return success for the CreateVolume Request and then PVC will be bound. Signed-off-by: Pawan <pawan@mayadata.io>
2020-05-18 16:30:20 +05:30
status:
state: Ready
Reference in a new issue Copy permalink