Pawan 25d1f1a413 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-21 08:49:57 +05:30
..
apis/openebs.io/zfs/v1alpha1	feat(zfspv): pvc should be bound only if volume has been created.	2020-05-21 08:49:57 +05:30
builder	feat(zfspv): pvc should be bound only if volume has been created.	2020-05-21 08:49:57 +05:30
client/k8s/v1alpha1	feat(topology): adding support for custom topology keys (#94)	2020-04-30 14:13:29 +05:30
common	feat(analytics): adding google analytics for ZFSPV	2020-03-02 23:00:22 +05:30
config	feat(zfs-localpv): initial commit	2019-09-18 08:44:08 +05:30
driver	feat(zfspv): pvc should be bound only if volume has been created.	2020-05-21 08:49:57 +05:30
generated	feat(zfspv): pvc should be bound only if volume has been created.	2020-05-21 08:49:57 +05:30
mgmt	feat(crd-gen): automate the CRDs generation with validations for APIs (#75)	2020-04-01 17:54:20 +05:30
response	feat(resize): adding Online volume expansion support for ZFSPV	2020-03-04 18:30:28 +05:30
usage	feat(analytics): adding google analytics for ZFSPV	2020-03-02 23:00:22 +05:30
version	feat(analytics): adding google analytics for ZFSPV	2020-03-02 23:00:22 +05:30
zfs	feat(zfspv): pvc should be bound only if volume has been created.	2020-05-21 08:49:57 +05:30