/etc/configs
└── config1
And the following tree will be mounted by k8s configmap
/etc/configs
└── config2
As a result - existing configuration files won't be visible, as long as configmap volume is mounted.
I thought about several solutions for this problem:
1. Mount each file from configmap separately (this information should be available when mounts are created in kubelet)
- it might be a problem with big amount of keys in configmap, and thus shouldnt be default behaviour
2. Use overlayfs/aufs and make necessary changes in docker
- still tricky to merge multiple configmaps into single directory
3. Mount configmap to another directory and copy them using init-container
- is it possible to mount configmap in init-container?
I believe this should be common thing, and probably someone already thought about it.
Is there any plans how to tackle this case, or maybe there is already a solution?
--
You received this message because you are subscribed to the Google Groups "kubernetes-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/5c462b3b-ac1a-46df-a19f-7b63e6e33226%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2nd, two files from different sources.There is use case with openstack services, i will add details in the morning.Sorry for confusion.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.