Feature state: 1.1.0
extraVolumeMounts value in Kubedeploy allow for defining additional mounted volumes for all containers in a Pod.
extraVolumeMounts in Kubedeploy will not mount any additional volumes.
Allowed volume mounts include:
existingClaim- this can be used to mount any chart external persistent volume claims in any type of deploymentMode. By chart's design only statefulset will have this ability
hostPath- can be used to mount any filesystem directories directly from Kubernetes node in Pod
HostPath volumes present many security risks, and it is a best practice to avoid the use of HostPaths when possible. When a HostPath volume must be used, it should be scoped to only the required file or directory, and mounted as ReadOnly.
csi- allows mounting any volumes exposed with csi drivers, for example secrets-store-csi-driver.
emptyDir- temporary empty directories for Pod's container to share (see emptyDir for more info).
secretName- allows mounting any chart external Secret objects. If you define secrets in chart, then it's suggested to use extraSecrets mount ability.
As a result of the above example, Kubdeploy will mount five additional volumes to all containers in Pod.
- existing volume claim with name
volume-claimwill be mounted at
/usr/shared/from Kubernetes node will be mounted at
csisecret would be mounted at
emptyDirwill be mounted at
my-secretwill be mounted at