ConfigFiles defines where the Kerberos configuration should be sourced from. Config files
will be placed into the `/etc/krb5.conf.rook/` directory.
If this is left empty, Rook will not add any files. This allows you to manage the files
yourself however you wish. For example, you may build them into your custom Ceph container
image or use the Vault agent injector to securely add the files via annotations on the
CephNFS spec (passed to the NFS server pods).
Rook configures Kerberos to log to stderr. We suggest removing logging sections from config
files to avoid consuming unnecessary disk space from logging to files.
volumeSource
object
configMap
object
emptyDir
object
sizeLimit
object
pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
hostPath
object
persistentVolumeClaim
object
claimName
string required
projected
object
sources
[]object
clusterTrustBundle
object
labelSelector
object
matchExpressions
[]object
configMap
object
downwardAPI
object
items
[]object
fieldRef
object
fieldPath
string required
resourceFieldRef
object
divisor
object
pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
podCertificate
object
certificateChainPath
string
credentialBundlePath
string
maxExpirationSeconds
integer
signerName
string required
secret
object
serviceAccountToken
object
expirationSeconds
integer
secret
object