OpenShift Volume Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
=The Volume Mechanism= | =The Volume Mechanism= | ||
Volumes are mounted filesystems available to [[OpenShift Concepts#Pod|pods]] and their [[OpenShift Concepts#Container|containers]]. Volumes may be backed by a number of host-local or network attached storage endpoints. The simplest volume type is [[#EmptyDir|EmptyDir]], which is a temporary directory on a single machine. Administrators may also allow to request and attach [[#Persistent_Volume|Persistent Volumes]]. | |||
Various contexts list the following objects as "volumes": [[#ConfigMap|configMap]] [[#Downward_API|downwardAPI]] [[#EmptyDir|emptyDir]] [[#HostPath|hostPath]] [[#NFS|nfs]] [[#Persistent_Volume_Claim|persistentVolumeClaim]] [[OpenShift_Secrets_Concepts#Overview|secret]]. | |||
=Volume Types= | =Volume Types= | ||
Revision as of 01:19, 6 February 2018
Internal
The Volume Mechanism
Volumes are mounted filesystems available to pods and their containers. Volumes may be backed by a number of host-local or network attached storage endpoints. The simplest volume type is EmptyDir, which is a temporary directory on a single machine. Administrators may also allow to request and attach Persistent Volumes.
Various contexts list the following objects as "volumes": configMap downwardAPI emptyDir hostPath nfs persistentVolumeClaim secret.