Kubernetes volume hostPath explained with examples

  • The hostPath volume mounts a resource from the host node filesystem. the resources could be directory, file socket, character, or block device. These resources mu
  • A hostPath volume mounts a file or directory from the host node’s filesystem into your pod.
  • A hostPath PersistentVolume must be used only in a single-node cluster. Kubernetes does not support hostPath on a multi-node cluster currently.
  • The directories created on the underlying hosts are only writable by root. You either need to run your process as root in a privileged container or modify the file permissions on the host to be able to write to a hostPath volume

Uses for a hostPath are:

  • This is not something that most Pods will need, but it offers a powerful escape hatch for some applications.
  • Deploying some Node Specific files through pod
  • Running a container that needs access to Docker internals; use a hostPath of /var/lib/docker
  • Allowing a Pod to specify whether a given hostPath should exist prior to the Pod running, whether it should be created, and what it should exist as


apiVersion: v1
kind: Pod
  name: test-pd
  - image: k8s.gcr.io/test-webserver
    name: test-container
    - mountPath: /test-pd
      name: test-volume
  - name: test-volume
      # directory location on host
      path: /data
      # this field is optional
      type: DirectoryOrCreate

Rajesh Kumar
Follow me