ceph-csi/charts/ceph-csi-cephfs/templates/csidriver-crd.yaml

{{ if semverCompare ">=1.18.0-beta.1" .Capabilities.KubeVersion.Version }}
apiVersion: storage.k8s.io/v1
{{ else }}
apiVersion: storage.k8s.io/v1beta1
{{ end }}
kind: CSIDriver
metadata:
  name: {{ .Values.driverName }}
spec:
  attachRequired: true
  podInfoOnMount: false
helm: fix k8s version string for csidriver crds semverCompare Current implementation of semvercompare fails against pre-release versions. This commit fixes it by using the entire version string at which csidriver api became GA. s\|">=1.18"\|">=1.18.0-beta.1" Fixes: #2039 Signed-off-by: Rakshith R <rar@redhat.com> 2021-05-10 10:46:14 +00:00			`{{ if semverCompare ">=1.18.0-beta.1" .Capabilities.KubeVersion.Version }}`
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`
			`{{ else }}`
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: 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			`{{ end }}`
Add csidriver CRD if attacher is not enabled, we need to create the csidriver CRD with spec to make attachRequired as false to skip volume attach check in kube. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2019-04-03 05:15:15 +00:00			`kind: CSIDriver`
			`metadata:`
			`name: {{ .Values.driverName }}`
			`spec:`
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			`attachRequired: true`
Add csidriver CRD if attacher is not enabled, we need to create the csidriver CRD with spec to make attachRequired as false to skip volume attach check in kube. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2019-04-03 05:15:15 +00:00			`podInfoOnMount: false`