Can Kubernetes service mount multiple “portions” of a single GCE disk at the multiple mount paths?

Drux asked:

I am defining my first Kubernetes deployment and would like to define a container that mounts persistent storage at two points, say like this (in Deployment.yaml inside spec.template.spec.containers.-):

- name: volume1
  mountPath: /var/log/app
- name: volume2
  mountPath: /var/lib/app

I understand from Kubernetes’ MEAN stack sample that I should be able to create two corresponding GCE disks, say like this:

gcloud compute disks create --size 10GB volume1
gcloud compute disks create --size 10GB volume2

I currently contemplate two disks instead of one only because I need to mount at two different paths. Can a Kubernetes service mount different “portions” (possibly partitions) of a single volume/disk at different paths?

The specification of v1.VolumeMount suggests that this may not be possible at the level of the service specification, because it supports only the fields name, readOnly, and mountPath.

These answers suggests that it might be possible on the level of EXT4 partitions, but that this would require the the volume to be read-only. Even in the read-only case (which does not meet my requirements), how would I go about creating a GCE disk with partitions?

(migrated from StackOverflow)

My answer:

A Kubernetes persistent volume (or GCE persistent disk, which is approximately the same thing) can only be mounted to one point in your pod’s directory structure. But once mounted, you can certainly create bind mounts or symbolic links to organize its files however you wish. You can also change the configuration of your applications to read and write to a subdirectory of wherever you mounted the persistent volume, but that would take more work.

View the full question and answer on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.