ceph-csi/api/deploy/kubernetes/nfs/csidriver.yaml

---
apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  name: "{{ .Name }}"
spec:
  attachRequired: false
  fsGroupPolicy: File
  volumeLifecycleModes:
    - Persistent
deploy: add CSIDriver for NFS The API is extended for generation of the NFS CSIDriver object. The YAML file under deploy/ was created by `yamlgen`. The contents of the csidriver.yaml file is heavily based on the upstream CSIDriver from the Kubernetes csi-driver-nfs project. Because ./tools/yamlgen uses the API, it gets copied under vendor/ . This causes two copies of the API to be included in the repository, but that can not be prevented, it seems. See-also: https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/deploy/csi-nfs-driverinfo.yaml Signed-off-by: Niels de Vos <ndevos@redhat.com> 2022-03-02 08:32:01 +00:00			`---`
			`apiVersion: storage.k8s.io/v1`
			`kind: CSIDriver`
			`metadata:`
			`name: "{{ .Name }}"`
			`spec:`
			`attachRequired: false`
deploy: add fsgrouppolicy to the driver yaml this fsgrouppolicy setting was missing in api/deploy/* which caused the yamlgen to not pickup this. this commit address the same. Signed-off-by: Humble Chirammal <hchiramm@redhat.com> 2022-11-11 07:15:00 +00:00			`fsGroupPolicy: File`
deploy: add CSIDriver for NFS The API is extended for generation of the NFS CSIDriver object. The YAML file under deploy/ was created by `yamlgen`. The contents of the csidriver.yaml file is heavily based on the upstream CSIDriver from the Kubernetes csi-driver-nfs project. Because ./tools/yamlgen uses the API, it gets copied under vendor/ . This causes two copies of the API to be included in the repository, but that can not be prevented, it seems. See-also: https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/deploy/csi-nfs-driverinfo.yaml Signed-off-by: Niels de Vos <ndevos@redhat.com> 2022-03-02 08:32:01 +00:00			`volumeLifecycleModes:`
			`- Persistent`