Control component ordering

[chicocvenancio]

Is your feature request related to a problem? Please describe.

Currently components are applied as a first step of any layer. That means any changes made by other transformers/generators are not available to it. This complicates a few patterns if a component is needed.

EG:
A diamond pattern like https://github.com/kubernetes-sigs/kustomize/blob/ec38bbeb999066abea59fd11c54e68377765a510/api/krusty/diamonds_test.go with components at kirk would fail if the components tries to reference kirk-storefront or spec.type. This means a new layer would be necessary to allow for components to be used, for each leg of the diamond (we have over 90 in our setup).

Describe the solution you'd like
Control to apply the component at the same level their operations would be applied if not in component, first or last. Perhaps a new field?

[k8s-ci-robot]

@chicocvenancio: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[KnVerey]

This won't be possible in Kustomization, but the good news is we have a KEP for a new kind called Composition that has arbitrary transformer/generator/validator ordering as one of its features.

• Kustomize Plugin Composition API KEP (Note that https://github.com/kubernetes/enhancements/pull/3097/files has some small changes to this)
• Prototype PR: Composition implementation prototype #4323, which has a complete implementation but lists several obstacles to merging that require a fair amount of investment to solve

[KnVerey]

Actually, my first sentence wasn't strictly correct. Come to think of it, the combination of Composition prerequisites #4403 and #4402 should allow you to define your own sequence of generators/transformers/validators in the existing transformers field in a Kustomization as well.

Since we already have plans that would make this possible tracked in those issues / the KEP, please follow along there instead.
/close

[k8s-ci-robot]

@KnVerey: Closing this issue.

In response to this:

Actually, my first sentence wasn't strictly correct. Come to think of it, the combination of Composition prerequisites #4403 and #4402 should allow you to define your own sequence of generators/transformers/validators in the existing transformers field in a Kustomization as well.

Since we already have plans that would make this possible tracked in those issues / the KEP, please follow along there instead.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[chicocvenancio]

Thanks for the links @KnVerey.