You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From kustomization c, I want to extend a configMap imported from resource b, where a name-prefix was added to a configMap originally defined in a. I expect to use b's name to denote the name of the configMap, but have to use a's instead. Full example:
Notice that if I use renamed-cm in c/kustomization.yaml, I get this error:
Error: merging from generator &{0xc0000eeb40 0xc0004d5a60 { } {map[] map[] false} {{ renamed-cm merge {[HELLO=WORLD] [] [] }}}}: id resid.ResId{Gvk:gvk.Gvk{Group:"", Version:"v1", Kind:"ConfigMap"}, Name:"renamed-cm", Namespace:""} does not exist; cannot merge or replace
This is not only confusing, it also means that one cannot define a base configMap, produce two different versions of it with namePrefix, and then extend only one (actually, one can't even extend both at the same time, since kustomize will fail with found multiple objects ... that could accept merge of ...).
$ kustomize version
Version: {KustomizeVersion:3.1.0 GitCommit:95f3303493fdea243ae83b767978092396169baf BuildDate:unknown GoOs:linux GoArch:amd64}
The text was updated successfully, but these errors were encountered:
When merging resources such as the output of a `configMapGenerator`,
we need to consider the `CurrentId`, otherwise, we cannot extend
a common base definition twice by adding different prefixes, and
then further kustomize them.
This fixeskubernetes-sigs#1442.
When merging resources such as the output of a `configMapGenerator`,
we need to consider the `CurrentId`, otherwise, we cannot extend
a common base definition twice by adding different prefixes, and
then further kustomize them.
This fixeskubernetes-sigs#1442.
jcpetruzza
added a commit
to jcpetruzza/kustomize
that referenced
this issue
Sep 10, 2019
When merging resources such as the output of a `configMapGenerator`,
we need to consider the `CurrentId`, otherwise, we cannot extend
a common base definition twice by adding different prefixes, and
then further kustomize them.
See kubernetes-sigs#1442.
From kustomization
c
, I want to extend aconfigMap
imported from resourceb
, where a name-prefix was added to aconfigMap
originally defined ina
. I expect to useb
's name to denote the name of theconfigMap
, but have to usea
's instead. Full example:Notice that if I use
renamed-cm
inc/kustomization.yaml
, I get this error:This is not only confusing, it also means that one cannot define a base
configMap
, produce two different versions of it withnamePrefix
, and then extend only one (actually, one can't even extend both at the same time, sincekustomize
will fail withfound multiple objects ... that could accept merge of ...
).The text was updated successfully, but these errors were encountered: