Replies: 1 comment
-
you have set a if your remove it and keep your transformer only, you'll have the transformer namespace applied as expected |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋,
I have configured a NamespaceTransformer to avoid namespace transformation for already set namespaces.
custom_namespace.yaml
My expectation is that manifests where the namespace is set would not be transformed anymore. I have this two kustomizations:
helm-release.yaml
helm-repository.yaml
kustomization.yaml
In the HelmRelease manifest, the namespace should be set by the transformer. In the HelmRepository the namespace should not be set because it is already set. But when I run
kustomize build .
I see this output.output.yaml
On both resources, the namespace would be set. Do I have a misunderstanding how the
unsetOnly
flag works? Or is there a configuration error on my site?Beta Was this translation helpful? Give feedback.
All reactions