-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
kubectl get and describe should work well with extensions #515
Comments
Client side and beta API targeted for 1.10 |
@smarterclayton @kubernetes/sig-cli-feature-requests @kubernetes/sig-api-machinery-feature-requests still on track for 1.10? |
We're trying to close the loop on the 1.10 plan |
@smarterclayton any progress? |
Yes, we are planning to bring this to beta in 1.10. Work is being tracked in kubernetes/kubernetes#58536 |
@smarterclayton sorry, I thought I had pinged you about this earlier. If this feature needs docs, can you please get a PR in in the next day or so? We need to merge all docs PRs by this Friday (March 9). If not, can you please indicate on the feature tracking spreadsheet? Thanks! |
@juanvallejo can you add a doc? |
@smarterclayton sure, will add doc |
@smarterclayton If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
@juanvallejo can you add details about the 1.11 planned things? I think we should try to get custom CRD columns on the server side in 1.11 with a minimal alpha api. I can bump the stable target to 1.12 |
The current tracking issue can be found in kubernetes/kubernetes#60712. |
Thanks for the update! |
/milestone v1.15 |
Hey, @soltysh @smarterclayton @juanvallejo 👋 I'm the v1.15 docs Lead. Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions |
It does not outside of api documentation. We probably want to review the
topic though.
On May 10, 2019, at 2:59 AM, Barnabas Makonda <[email protected]> wrote:
Hey, @soltysh <https://github.com/soltysh> @smarterclayton
<https://github.com/smarterclayton> @juanvallejo
<https://github.com/juanvallejo> 👋 I'm the v1.15 docs Lead.
Does this enhancement require any new docs (or modifications)?
Just a friendly reminder we're looking for a PR against k/website (branch
dev-1.15) due by Thursday, May 30th. It would be great if it's the start of
the full documentation, but even a placeholder PR is acceptable. Let me
know if you have any questions
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#515 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI37J3XVUT5E7QM2QH5QZDPUUMMPANCNFSM4EEZMI2Q>
.
|
@smarterclayton Noted. so this means it won't require any PR submitted to k/website |
Hi @smarterclayton . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open. Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone. The one I currently see in this issue is kubernetes/kubernetes#76789. Let me know if there are missing ones. If you know this will slip, please reply back and let us know. Thanks! |
Hi @smarterclayton @soltysh , today is code freeze for the 1.15 release cycle. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception. |
And was marked LGTM
On May 30, 2019, at 10:06 AM, Kendrick Coleman <[email protected]> wrote:
Hi @smarterclayton <https://github.com/smarterclayton> @soltysh
<https://github.com/soltysh> , today is code freeze for the 1.15 release
cycle. I do not see a reply for any k/k PRs to track for this merge. It's
now being marked as At Risk in the 1.15 Enhancement Tracking Sheet
<https://docs.google.com/spreadsheets/d/1Vc949C4iC2f8GTmjfJkX04VUNcbimhg8ujp1bUAjGK4/edit?ts=5cb282ad#gid=0>.
If there is no response, or you respond with PRs to track and they are not
merged by EOD PST, this will be dropped from the 1.15 Milestone. After this
point, only release-blocking issues and PRs will be allowed in the
milestone with an exception.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#515?email_source=notifications&email_token=AAI37JYG26Y34S323D6FKM3PX7NPVA5CNFSM4EEZMI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSNLDQ#issuecomment-497341838>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI37J7UEYJO2Q5IHPADS3DPX7NPVANCNFSM4EEZMI2Q>
.
|
The only PR for 1.15 is
kubernetes/kubernetes#77817 (comment)
And is still on track to merge today.
On May 30, 2019, at 10:06 AM, Kendrick Coleman <[email protected]> wrote:
Hi @smarterclayton <https://github.com/smarterclayton> @soltysh
<https://github.com/soltysh> , today is code freeze for the 1.15 release
cycle. I do not see a reply for any k/k PRs to track for this merge. It's
now being marked as At Risk in the 1.15 Enhancement Tracking Sheet
<https://docs.google.com/spreadsheets/d/1Vc949C4iC2f8GTmjfJkX04VUNcbimhg8ujp1bUAjGK4/edit?ts=5cb282ad#gid=0>.
If there is no response, or you respond with PRs to track and they are not
merged by EOD PST, this will be dropped from the 1.15 Milestone. After this
point, only release-blocking issues and PRs will be allowed in the
milestone with an exception.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#515?email_source=notifications&email_token=AAI37JYG26Y34S323D6FKM3PX7NPVA5CNFSM4EEZMI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSNLDQ#issuecomment-497341838>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI37J7UEYJO2Q5IHPADS3DPX7NPVANCNFSM4EEZMI2Q>
.
|
This has graduated to stable and been implemented. Time to close /milestone clear |
@kacole2: Closing this issue. In response to this:
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/test-infra repository. |
The describe part of this enhancement isn't implemented, yet. /re-open |
/reopen |
@pacoxu: Reopened this issue. In response to this:
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/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
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/test-infra repository. |
Feature Description
As part of the split of kubectl from close coupling with the repository, and to allow better extensibility, it should be possible for third party API extensions and CRD to provide custom output for
kubectl get
to avoidkubectl
having to have code to interpret those resources. We will move the printing to the server side, and kubectl will retrieve results. We also wish to move describe in a future release.The text was updated successfully, but these errors were encountered: