<p>I'm trying to adapt my Spring boot application to k8s environment and want to use ConfigMaps as property sources.
I faced that if I'm using</p>
<pre><code>      kubernetes:
        config:
          sources:
            - name: application-config
</code></pre>
<p>for application with name <code>appName</code> then any other ConfigMaps with Spring cloud kubernetes convention names like <code>appName-kubernetes</code> or <code>appName-dev</code> is silently ignored. Looks like listed sources in <code>config.sources</code> overrides and disables usage of any other PropertySources from ConfigMaps. <br>
I'm forced to use specific name for ConfigMap ('application-config' in sample above). <p>
So question is - how (if) can I specify both <code>config.sources</code> and simultaneously have ConfigMaps with names <code>appName-*</code> picked up correctly?</p>

Владимир Сухарев
<p>After some debugging through ConfigMapPropertySource achieved this by</p>
<pre><code>    kubernetes:
      config:
        sources:
          - name: application-config
          - name: @project.artifactId@
        name: @project.artifactId@
</code></pre>
<p>Now it loads <code>application-config</code>, <code>application-config-kubernetes</code>, <code>appName-kubernetes</code> and other profile-specific ConfigMaps.</p>
