Applications such as WordPress or MySQL require the use of data persistence. It is common when deploying such applications to use a HostPath volume as it is agnostic from the platform. A HostPath volume shares the filesystem of the Host within the container making the data available between pod restarts. However, it ties the data to one node only, creating a single point of failure and restricting any kind of scalability. Kubernetes is not able to schedule the application in any other node even if it is unavailable. This leads to eventual data loss.