chore(deps): update dependency kubernetes-sigs/kustomize to v5.1.0 #56
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/kubernetes-sigs-kustomize-5.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v5.0.3
->v5.1.0
Release Notes
kubernetes-sigs/kustomize
v5.1.0
Compare Source
Highlights
Components are now applied after generators: https://github.com/kubernetes-sigs/kustomize/pull/5170
We made this change cautiously as we want to avoid user friction when updating kustomize; however we felt that it is a bug that resources from
resources
and resources from generators are treated differently. Given that components is currently an alpha feature, we felt that now was the time to adjust if ever.We are currently working on on https://github.com/kubernetes-sigs/kustomize/issues/4402, which will make the ordering of
resources
,components
, and other generators customizable in the kustomization file. Please use that issue for tracking if you are blocked from upgrading kustomize for this reason, and we hope to have it available soon.See https://github.com/kubernetes-sigs/kustomize/issues/5141 for more detailed discussion.
Bug fixes:
#5030:
kustomize edit
will return an error if there is no matching path#5170: components are now applied after generators
Dependency updates
#5186: Update gnostic dependency with gnostic-models
#5187: Bump to go 1.20
#5212: pin to kyaml v0.14.3
#5213: pin to cmd/config v0.11.3
#5214: pin to api 0.14.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.