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
Add subresource support to kubectl #2590
Comments
/stage alpha |
Hi @nikhita , 1.22 enhancements team here! For the enhancement to be included in the milestone, it must meet the following criteria:
In order to move forward in 1.22 we'd need to get the KEP merged as well as a production readiness review before enhancements freeze on 5/13. Let us know if there's anything we can do to help before then. Thanks!! |
Hi @salaxander, @nikhita and I are working in this together. Regarding the production readiness review, the KEP doc has a section by the same name. Does this section satisfy the required criteria? If not, can you let us know what is missing from it. |
Hi @ykakarap! - Here's the full documentation on the production readiness review process -> https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md |
#2600 merged so we should be all good now. |
Hi @nikhita 👋 1.22 Docs Shadow here. Please follow the steps detailed in the documentation to open a PR against dev-1.22 in the kubernetes/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thank you! |
@chrisnegus Thanks for the heads-up! :) Will follow the steps to do it. |
Hey @salaxander the final PR will be read in a day or 2. |
Hey @salaxander, this is the corresponding PR: kubernetes/kubernetes#99556. |
Hi @ykakarap - One more check-in as we're a week away from code freeze. Any updates on if you expect kubernetes/kubernetes#99556 to merge before the deadline? Thanks! |
Hi @salaxander, I expect the PR to be merged before the deadline. SIG CLI has already reviewed the code. cc @nikhita |
Hey @ykakarap - I see the PR is approved, but there are merge conflicts at the moment. It'll need to merge before code freeze tomorrow evening to be included in 1.22. Let us know if there's anything we can do to help :) |
@salaxander thanks for offering to help :) There is still some work that needs to be done before the PR can be merged. |
@nikhita @salaxander Friendly reminder about the upcoming docs placeholder PR deadline tomorrow |
@salaxander @ritpanjw We are planning to move this enhancement to the next release. Please let me know if there is anything I need to do to note that. |
Hi @ykakarap - I'll update it in our tracking, thanks for letting me know! |
/milestone v1.23 |
Oh, I didn't know scale was supported! That was what I was thinking. |
Wait:
Am I doing it wrong? |
With #3729 merged this enhancement is ready to be |
@thockin ah, good catch! It looks like edit was deliberately written to not support To be honest, I can't remember why we decided to do this but I'll follow up on this to either: 1) add support or 2) document this behavior. scale is supported for get, patch and replace commands though! |
Hi @MadhavJivrajani @nikhita, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. Please feel free to reach out with any questions. Thanks! |
Hi @nikhita 👋,
Please let me know what PRs in k/k I should be tracking for this KEP. |
Hi @shatoboar
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/label lead-opted-in |
Hello @nikhita 👋, Enhancements team here. Just checking in as we approach enhancements freeze on [02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca):. This enhancement is targeting for stage Here's where this enhancement currently stands:
The only thing left to do is to merge: #4468. Please let me know when you've done so. The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you! |
@mickeyboxell based on slack discussion with @MadhavJivrajani we'll taking this out from 1.30 cycle, we'll push this over to 1.31 /remove-label lead-opted-in |
/milestone clear |
Enhancement Description
--subresource
to kubectl commands like get, patch, edit and replace commands to allow fetching and updating subresources like status, scale, etc.k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):/sig cli
/assign @nikhita @ykakarap
cc @eddiezane @soltysh @seans3 @pwittrock
The text was updated successfully, but these errors were encountered: