Managing Persistent Volume Claims and UIDs with Kubernetes/Docker

I am deploying Elasticsearch 5.2.1 as a docker container, managed under kubernetes.

I use managed network storage to back all the Elasticsearch data. Kubernetes is happy to create/format/mount/remount volumes through a containers whole life cycle. With the change in 5 to always run without root, how are people managing UIDs in a distributed environment?

I am mostly unfamiliar with docker's "run as" functionality, where the docker image has a local user account and runs under that non-root account. How does that impact file ownership in the situation where a container is moved to another host?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.