-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-2590: graduate kubectl subresource support to beta #3729
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
Conversation
29703cf to
12ec0b6
Compare
12ec0b6 to
dba604b
Compare
|
User feedback here: This feature is a must and has been a life saver for a while to me. Previously I've been using kubectl-edit_status plugin, and as soon as this feature was released on kubectl I've just migrated directly to it. I have faced no problem so far, or inconsistency on the behavior. Just using Nice work folks! |
soltysh
left a comment
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.
I'd also suggest updating the KEP to use the new template https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md
|
|
||
| #### Beta | ||
|
|
||
| - Add the `--subresource` flag to the apply command. |
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.
I'm not quite convinced we want to support --subresource in apply command, given its general purpose of being a declarative command, which we covered in this presentation https://youtu.be/eOxy1PS5TyQ?t=780.
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.
I'm not quite convinced we want to support --subresource in apply command
It's also not straightforward to implement. Ref: #2600 (comment), #2600 (comment)
Is it ok to move this KEP to beta without adding --subresource support for apply?
Although, then I'm not sure what "beta" or "GA" for this feature would even mean 🤔
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.
I'm not quite convinced we want to support --subresource in apply command
It's also not straightforward to implement. Ref: #2600 (comment), #2600 (comment)
Is it ok to move this KEP to beta without adding
--subresourcesupport for apply?
It's totally fine, just add a note, that due to additional complexity and the nature of kubectl apply command we've decided not to expand it with this flag.
Although, then I'm not sure what "beta" or "GA" for this feature would even mean thinking
You can promote to beta, w/o any test, which can be added during promotion, or after. For GA we need tests covering every are, ideally unit, integration (cmd) and e2e.
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.
Addressed feedback and updated to the new KEP template.
dba604b to
d0d40b5
Compare
soltysh
left a comment
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.
one nit, but otherwise this lgtm
|
|
||
| #### GA | ||
|
|
||
| - e2e tests are added. |
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.
These tests are required for GA, so you want them being added at beta stage, since that will be one of reqs for GA promotion.
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.
Updated.
d0d40b5 to
a3b7f20
Compare
|
/assign @johnbelamaric |
soltysh
left a comment
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
/approve
from sig-cli pov
|
Hi @nikhita, Production Readiness Review Shadows are going to do first pass PRR reviews this cycle (recently announced here), I'll be shadowing this KEP and |
| #### Beta | ||
|
|
||
| - Gather feedback from users. | ||
| - e2e tests are added. |
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.
🎉
| #### Alpha | ||
|
|
||
| - [ ] Collect user feedback on adding support of `--subresource` for `apply` | ||
| - Add the `--subresource` flag to get, patch, edit and replace commands. |
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.
Also unit tests?
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.
Added unit and integration tests.
a3b7f20 to
505daaa
Compare
soltysh
left a comment
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
|
In alpha, looks like we didn't make you set an env var in order to make the flag valid. Usually we do that now for kubectl. It is essentially a positive acknowledgement by the user that "I know I am using an alpha feature". That's fine, no change needed now. But in the future that would be the right approach. /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric, nikhita, 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 |
Yeah, that's my bad, I usually ensure that we have it behind an env var 😞 Sorry for that. |
One-line PR description:
We’ve received good feedback for this feature and would like to move it to beta in v1.27. Some examples of feedback:
Issue link: #2590
/assign @soltysh
cc @MadhavJivrajani