<p>As per the documentation at - <a href="https://github.com/spring-cloud-incubator/spring-cloud-kubernetes/#configmap-propertysource" rel="nofollow noreferrer">https://github.com/spring-cloud-incubator/spring-cloud-kubernetes/#configmap-propertysource</a>, it is possible to make ConfigMaps available during application bootstrapping through adding <code>spring.cloud.kubernetes.config.name</code> to the <code>bootstrap.yaml/properties</code>.</p>

<p>Is it possible to consume multiple ConfigMaps in this manner? </p>

<p>I believe it is possible to do this in the pod specification through the use of <code>env-from</code> - <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/</a>. But it would be great to do this with the current setup that we have. </p>

<p>As you can see in <a href="https://github.com/fabric8io/spring-cloud-kubernetes/blob/master/spring-cloud-kubernetes-core/src/main/java/io/fabric8/spring/cloud/kubernetes/config/ConfigMapPropertySource.java" rel="nofollow noreferrer">ConfigMapPropertySource.java</a>, only one ConfigMap will be used by this property source.</p>

<p>However, using <code>envFrom</code>, all entries in a ConfigMap can be provided as environment variables to the container and <a href="https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html" rel="nofollow noreferrer">Spring Boot can also read environment variables</a>, so maybe this will help you.</p>
