Ed Overton

A quick note that [the documentation states](https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/configmapgenerator/#overriding-base-configmap-values): > **Name suffixing with overlay configMapGenerator** > When using configMapGenerator to override values of an existing ConfigMap, the overlay configMapGenerator does not cause...

@tcurdt, as far as I'm aware, the issue is that the merge behavior honors the original ConfigMap. If the original ConfigMap was generated, then a merge rebuilds the suffix based...

I follow. I don't think it's worth digging down into my example. It was to show how to leverage current behavior to get the result you want, but that's not...

[This feature is available](https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/configmapgenerator/) via `options`, which basically is a per-generator `generatorOptions`: kustomization.yaml ```yaml configMapGenerator: - name: grafana-dashboard-has-label options: labels: grafana_dashboard: "1" literals: - key=value - name: other-configmap-lacks-label literals: -...

It looks like the issue is that the base and overlay disagree on whether an absent field path should be created. `kustomize` cannot merge the two configurations cleanly since [it...

@stormqueen1990, here's what I used for investigation. ``` $ kustomize-v5.0.1 build overlay Error: merging config failed to merge CommonLabels fieldSpec: conflicting fieldspecs $ ``` Note that v5.4.3 has the some...