Open sanmai-NL opened 11 months ago
@ncapps Could you please investigate how components work with respect to the ordering of transformers (in this case the namespace transformer) and report back? Ideally we will understand how it works, rationalize it, and then decide whether to change or document the behavior.
Here is a starting point for where to look in the code: https://github.com/kubernetes-sigs/kustomize/blob/ab519fdc13ded9875e42d70ac8a5b1b9023a2dbb/api/internal/target/kusttarget.go#L232
Here is the KEP for the original design of components: https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1802-kustomize-components
/assign @ncapps
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@ncapps What's the status?
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/reopen
@sanmai-NL: Reopened this issue.
/remove-lifecycle rotten
What happened?
When using a Base, and perhaps Overlay, the
namespace
field inkustomization.yml
is applied to all Resources. When adding a Resource from a Component, itskustomization.yml
has to repeat thenamespace
field.What did you expect to happen?
Either
namespace
is inherited, optionally controlled, and/or the behavior is documented.How can we reproduce it (as minimally and precisely as possible)?
Expected output
Actual output
Kustomize version
v5.1.1
Operating system
MacOS