-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-4951: clarify which API versions are impacted by the change. #5217
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
KEP-4951: clarify which API versions are impacted by the change. #5217
Conversation
Hi @jm-franc. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign @gjtempleton |
/lgtm |
Thanks for this. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gjtempleton, jm-franc 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 |
@jm-franc Is there a plan to promote this to beta in 1.34? It's a pretty cool feature, thanks for implementing it. 🙂 |
Thank you and yes, that's what I'm aiming for. |
Awesome, thanks for the answer. Looking forward to it. |
Clarify that only the v2 API will support the new field, and how other versions will implement round-trip requirements.