A mount point is the path inside a container where a Pod volume becomes available. Kubernetes defines the volume separately in the Pod, then connects it to a container through that container’s volumeMounts array. This lets application files live in a volume instead of the container’s perishable filesystem. section 9.2.1
A volume mount definition normally specifies:
- name: the volume name, which must match a volume defined in the Pod. section 9.2.1
- mountPath: the path inside the container where Kubernetes mounts the volume. section 9.2.1
- readOnly: whether the container receives a read-only mount; it defaults to false. section 9.2.1
Mounting an emptyDir volume
The Pod defines a volume named quiz-data, and the mongo container mounts that volume at /data/db. MongoDB therefore writes its files to the volume rather than the container filesystem. spec: volumes: - name: quiz-data emptyDir: {} containers: - name: mongo image: mongo volumeMounts: - name: quiz-data mountPath: /data/db section 9.2.1
Mounts can connect different containers to shared data at different paths. An init container can write files to a mounted volume, after which a main container reads them. Secret volumes use the same pattern; for example, certificate files can be mounted read-only at /etc/certs. section 9.2.2 section 9.5.3
