ceph-csi/deploy/cephfs/kubernetes/csidriver.yaml

---
# if Kubernetes version is less than 1.18 change
# apiVersion to storage.k8s.io/v1beta1
apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  name: cephfs.csi.ceph.com
spec:
  attachRequired: false
  podInfoOnMount: false
  fsGroupPolicy: File
deploy: add csidriver object for cephfs and rbd csidriver object can be created on the kubernetes for below reason. If a CSI driver creates a CSIDriver object, Kubernetes users can easily discover the CSI Drivers installed on their cluster (simply by issuing kubectl get CSIDriver) Ref: https://kubernetes-csi.github.io/docs/csi-driver-object.html#what-is-the-csidriver-object attachRequired is always required to be set to true to avoid issue on RWO PVC. more details about it at https://github.com/rook/rook/pull/4332 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-03-30 05:33:01 +00:00			`---`
			`# if Kubernetes version is less than 1.18 change`
cleanup: fix beta apiVersion for csidriver This change resolves a typo for installing the CSIDriver resource in Kubernetes clusters before 1.18, where the apiVersion is incorrect. See also: https://kubernetes-csi.github.io/docs/csi-driver-object.html [ndevos: replace v1betav1 in examples with v1beta1] Signed-off-by: Thomas Kooi <t.j.kooi@avisi.nl> 2021-07-13 19:21:56 +00:00			`# apiVersion to storage.k8s.io/v1beta1`
deploy: add csidriver object for cephfs and rbd csidriver object can be created on the kubernetes for below reason. If a CSI driver creates a CSIDriver object, Kubernetes users can easily discover the CSI Drivers installed on their cluster (simply by issuing kubectl get CSIDriver) Ref: https://kubernetes-csi.github.io/docs/csi-driver-object.html#what-is-the-csidriver-object attachRequired is always required to be set to true to avoid issue on RWO PVC. more details about it at https://github.com/rook/rook/pull/4332 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-03-30 05:33:01 +00:00			`apiVersion: storage.k8s.io/v1`
			`kind: CSIDriver`
			`metadata:`
			`name: cephfs.csi.ceph.com`
			`spec:`
deploy: remove `attachrequired` param from csidriver object As the attacher is no longer required we have to mention the same for csidriver object parameter. Signed-off-by: Humble Chirammal <hchiramm@redhat.com> 2022-06-02 04:34:48 +00:00			`attachRequired: false`
deploy: add csidriver object for cephfs and rbd csidriver object can be created on the kubernetes for below reason. If a CSI driver creates a CSIDriver object, Kubernetes users can easily discover the CSI Drivers installed on their cluster (simply by issuing kubectl get CSIDriver) Ref: https://kubernetes-csi.github.io/docs/csi-driver-object.html#what-is-the-csidriver-object attachRequired is always required to be set to true to avoid issue on RWO PVC. more details about it at https://github.com/rook/rook/pull/4332 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-03-30 05:33:01 +00:00			`podInfoOnMount: false`
cephfs: go with default permissions while creating subvolumes While creating subvolumes, CephFS driver set the mode to `777` and pass it along to go ceph apis which cause the subvolume permission to be on 777, however if we create a subvolume directly in the ceph cluster, the default permission bits are set which is 755 for the subvolume. This commit try to stick to the default behaviour even while creating the subvolume. This also means that we can work with fsgrouppolicy set to `File` in csiDriver object which is also addressed in this commit. Signed-off-by: Humble Chirammal <hchiramm@redhat.com> 2022-03-10 12:43:05 +00:00			`fsGroupPolicy: File`