sortOrderTransformer sorts builtins before CRDs by default #5490
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Eschewed features
What would you like to have added?
Builtin resource kinds should be ordered before CRDs by default.
Why is this needed?
CRDs may have dependencies on builtins such as Namespace. If Kustomize were to order builtins before CRDs by default, then users would not need to explicitly configure the resource order using the
sortOptions
field. This improves the kustomize user experience and reduces amount of configuration required for most use cases.Can you accomplish the motivating task without this feature, and if so, how?
Yes. A user can use the
sortOptions
field withorder: fifo
to configure the order of resources returned by kustomize build.What other solutions have you considered?
I have not considered other solutions. This is a minor enhancement to the default sort order.
Anything else we should know?
No response
Feature ownership
The text was updated successfully, but these errors were encountered: