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

#
# /!\ DO NOT MODIFY THIS FILE
#
# This file has been automatically generated by Ceph-CSI yamlgen.
# The source for the contents can be found in the api/deploy directory, make
# your modifications there.
#
---
apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  name: "nfs.csi.ceph.com"
spec:
  attachRequired: false
  volumeLifecycleModes:
    - Persistent
  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			`#`
			`# /!\ DO NOT MODIFY THIS FILE`
			`#`
			`# This file has been automatically generated by Ceph-CSI yamlgen.`
			`# The source for the contents can be found in the api/deploy directory, make`
			`# your modifications there.`
			`#`
			`---`
			`apiVersion: storage.k8s.io/v1`
			`kind: CSIDriver`
			`metadata:`
			`name: "nfs.csi.ceph.com"`
			`spec:`
			`attachRequired: false`
			`volumeLifecycleModes:`
			`- Persistent`
deploy: update fsGroupPolicy to File for nfs driver object NFS volume similar to CephFs volumes can support fsGroupPolicy as File, now Kubernetes Kubernetes may use fsGroup to change permissions and ownership of the volume to match user requested fsGroup in the pod's SecurityPolicy regardless of fstype or access mode. Signed-off-by: Rakshith R <rar@redhat.com> 2022-08-08 06:38:13 +00:00			`fsGroupPolicy: File`