-
Notifications
You must be signed in to change notification settings - Fork 394
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
✨ Rebase Kubernetes 1.31 #3160
✨ Rebase Kubernetes 1.31 #3160
Conversation
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.
Couple of nits, but overall looking really solid 👍🏻
83c4d36
to
c1cbca3
Compare
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.
/lgtm
I'd just be very happy about a PR description documenting what had to be done for the 1.31 upgrade :)
LGTM label has been added. Git tree hash: 9290a2a43cf327d50020760b880886f4a0518678
|
Added but needed to think what to add as it was so smooth :D |
0cd44fd
to
fd4b4c6
Compare
fd4b4c6
to
903e0a6
Compare
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
LGTM label has been added. Git tree hash: f4171e6e103314fa8dea225773c0f6f065ff99fd
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik 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 |
Summary
In general, this was very smooth sailing. So smooth Im worried I missed something bit :)
Full diff can be found here, where I tool baseline 1.31 and this PR shows diff we currently carry as of 1.31 rebase:
https://github.com/kcp-dev/kubernetes/pull/147/commits
In general, most fixes were machinery-related:
In general a lot of sed/replace type of work.
Biggest issues still is code-generation, where we are on our own :)
Related issue(s)
Fixes #
Release Notes