New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script kubectl kustomize update process #108857
Script kubectl kustomize update process #108857
Conversation
52d6afe
to
be5e145
Compare
/lgtm |
/assign @soltysh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/sig cli
/triage accepted
/priority backlog
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: KnVerey, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR scripts the manual process outlined in the Kustomize release docs. Demo: KnVerey#1. I chose hack/ as the location for this script since it uses utilities from there and invokes several of that directory's scripts. Let me know if it belongs somewhere else.
Which issue(s) this PR fixes:
None, but this related to kubernetes-sigs/kustomize#3952
Special notes for your reviewer:
This is split out of #108817. As discussed here, it is possible that a newer kyaml release will exist than the one we want to bring in. However, that is rare, and made even more unlikely by our typical release process. We can make the script accommodate version overrides in the future if needed, but Kustomize maintainers feel manual confirmation of the targeted versions is sufficient for the time being.
Does this PR introduce a user-facing change?