diff --git a/Documentation/CRDs/specification.md b/Documentation/CRDs/specification.md index 30b5575d8..32a2fb6f0 100644 --- a/Documentation/CRDs/specification.md +++ b/Documentation/CRDs/specification.md @@ -4288,6 +4288,119 @@ blocking deletion.

+

ConfigFileVolumeSource +

+

+(Appears on:KerberosConfigFiles, KerberosKeytabFile, SSSDSidecarAdditionalFile, SSSDSidecarConfigFile) +

+
+

Represents the source of a volume to mount. +Only one of its members may be specified. +This is a subset of the full Kubernetes API’s VolumeSource that is reduced to what is most likely +to be useful for mounting config files/dirs into Rook pods.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldDescription
+hostPath
+ + +Kubernetes core/v1.HostPathVolumeSource + + +		 +(Optional) +

hostPath represents a pre-existing file or directory on the host +machine that is directly exposed to the container. This is generally +used for system agents or other privileged things that are allowed +to see the host machine. Most containers will NOT need this. +More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath

+
+
+emptyDir
+ + +Kubernetes core/v1.EmptyDirVolumeSource + + +		 +(Optional) +

emptyDir represents a temporary directory that shares a pod’s lifetime. +More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir

+
+secret
+ + +Kubernetes core/v1.SecretVolumeSource + + +		 +(Optional) +

secret represents a secret that should populate this volume. +More info: https://kubernetes.io/docs/concepts/storage/volumes#secret

+
+persistentVolumeClaim
+ + +Kubernetes core/v1.PersistentVolumeClaimVolumeSource + + +		 +(Optional) +

persistentVolumeClaimVolumeSource represents a reference to a +PersistentVolumeClaim in the same namespace. +More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims

+
+configMap
+ + +Kubernetes core/v1.ConfigMapVolumeSource + + +		 +(Optional) +

configMap represents a configMap that should populate this volume

+
+projected
+ + +Kubernetes core/v1.ProjectedVolumeSource + + +		 +

projected items for all in one resources secrets, configmaps, and downward API

+

ConnectionsSpec

@@ -6239,15 +6352,16 @@ string volumeSource
- -Kubernetes core/v1.VolumeSource + +ConfigFileVolumeSource -

VolumeSource accepts a standard Kubernetes VolumeSource for Kerberos configuration files like -what is normally used to configure Volumes for a Pod. For example, a ConfigMap, Secret, or -HostPath. The volume may contain multiple files, all of which will be loaded.

+

VolumeSource accepts a pared down version of the standard Kubernetes VolumeSource for +Kerberos configuration files like what is normally used to configure Volumes for a Pod. For +example, a ConfigMap, Secret, or HostPath. The volume may contain multiple files, all of +which will be loaded.

@@ -6272,14 +6386,15 @@ HostPath. The volume may contain multiple files, all of which will be loaded.

volumeSource
- -Kubernetes core/v1.VolumeSource + +ConfigFileVolumeSource -

VolumeSource accepts a standard Kubernetes VolumeSource for the Kerberos keytab file like -what is normally used to configure Volumes for a Pod. For example, a Secret or HostPath. +

VolumeSource accepts a pared down version of the standard Kubernetes VolumeSource for the +Kerberos keytab file like what is normally used to configure Volumes for a Pod. For example, +a Secret or HostPath. There are two requirements for the source’s content: 1. The config file must be mountable via subPath: krb5.keytab. For example, in a Secret, the data item must be named krb5.keytab, or items must be defined to @@ -9596,16 +9711,16 @@ will be placed. Each subPath definition must be unique and must not contain &lsq volumeSource
- -Kubernetes core/v1.VolumeSource + +ConfigFileVolumeSource -

VolumeSource accepts standard Kubernetes VolumeSource for the additional file(s) like what is -normally used to configure Volumes for a Pod. Fore example, a ConfigMap, Secret, or HostPath. -Each VolumeSource adds one or more additional files to the SSSD sidecar container in the -/etc/sssd/rook-additional/<subPath> directory. +

VolumeSource accepts a pared down version of the standard Kubernetes VolumeSource for the +additional file(s) like what is normally used to configure Volumes for a Pod. Fore example, a +ConfigMap, Secret, or HostPath. Each VolumeSource adds one or more additional files to the +SSSD sidecar container in the /etc/sssd/rook-additional/<subPath> directory. Be aware that some files may need to have a specific file mode like 0600 due to requirements by SSSD for some files. For example, CA or TLS certificates.

@@ -9632,15 +9747,16 @@ by SSSD for some files. For example, CA or TLS certificates.

volumeSource
- -Kubernetes core/v1.VolumeSource + +ConfigFileVolumeSource -

VolumeSource accepts a standard Kubernetes VolumeSource for the SSSD configuration file like -what is normally used to configure Volumes for a Pod. For example, a ConfigMap, Secret, or -HostPath. There are two requirements for the source’s content: +

VolumeSource accepts a pared down version of the standard Kubernetes VolumeSource for the +SSSD configuration file like what is normally used to configure Volumes for a Pod. For +example, a ConfigMap, Secret, or HostPath. There are two requirements for the source’s +content: 1. The config file must be mountable via subPath: sssd.conf. For example, in a ConfigMap, the data item must be named sssd.conf, or items must be defined to select the key and give it path sssd.conf. A HostPath directory must have the sssd.conf file. @@ -10805,5 +10921,5 @@ string

Generated with gen-crd-api-reference-docs -on git commit e3d8da9a9. +on git commit 7fc93177e.