sortOrderTransformer sorts builtins before CRDs by default

[ncapps]

Eschewed features

• [X] This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

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

• [X] I am interested in contributing this feature myself! 🎉

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[stormqueen1990]

/remove-lifecycle stale /lifecycle frozen

[stormqueen1990]

/triage accepted