Skip to content
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

Jump to bottom

kubectl get and describe should work well with extensions #515

Closed
smarterclayton opened this issue Nov 21, 2017 · 48 comments
Closed

kubectl get and describe should work well with extensions #515

smarterclayton opened this issue Nov 21, 2017 · 48 comments
Assignees
@soltysh @smarterclayton @juanvallejo
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status

Comments

@smarterclayton
Copy link
Contributor

smarterclayton commented Nov 21, 2017 •
edited by kacole2

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 avoid kubectl 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.
@smarterclayton smarterclayton added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Nov 21, 2017
@smarterclayton smarterclayton added this to the next-milestone milestone Nov 21, 2017
@smarterclayton smarterclayton self-assigned this Nov 21, 2017
@smarterclayton
Copy link
Contributor Author

Client side and beta API targeted for 1.10

@idvoretskyi
Copy link
Member

@smarterclayton @kubernetes/sig-cli-feature-requests @kubernetes/sig-api-machinery-feature-requests still on track for 1.10?

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 15, 2018
@smarterclayton
Copy link
Contributor Author

We're trying to close the loop on the 1.10 plan

@tamalsaha tamalsaha mentioned this issue Jan 16, 2018
Open
@idvoretskyi
Copy link
Member

@smarterclayton any progress?

@smarterclayton
Copy link
Contributor Author

Yes, we are planning to bring this to beta in 1.10. Work is being tracked in kubernetes/kubernetes#58536

@smarterclayton smarterclayton modified the milestones: next-milestone, v1.10 Jan 22, 2018
@munnerz munnerz mentioned this issue Jan 24, 2018
Closed
@idvoretskyi idvoretskyi added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 29, 2018
@Bradamant3
Copy link
Contributor

@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!

@smarterclayton
Copy link
Contributor Author

@juanvallejo can you add a doc?

@juanvallejo
Copy link
Contributor

@smarterclayton sure, will add doc

@juanvallejo juanvallejo mentioned this issue Mar 7, 2018
Merged
@zytek zytek mentioned this issue Apr 10, 2018
Closed
@justaugustus
Copy link
Member

@smarterclayton
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

cc @idvoretskyi

@smarterclayton smarterclayton added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Apr 18, 2018
@smarterclayton smarterclayton modified the milestones: v1.10, v1.11 Apr 18, 2018
@smarterclayton
Copy link
Contributor Author

@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

@soltysh
Copy link
Contributor

soltysh commented Apr 18, 2018

The current tracking issue can be found in kubernetes/kubernetes#60712.
+1 for bumping this to stable in 1.12.

@kacole2
Copy link
Contributor

kacole2 commented Apr 29, 2019

/milestone v1.15

@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 29, 2019
@kacole2 kacole2 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 29, 2019
@makoscafee
Copy link

Hey, @soltysh @smarterclayton @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

@smarterclayton
Copy link
Contributor Author

smarterclayton commented May 10, 2019 via email

@makoscafee
Copy link

@smarterclayton Noted. so this means it won't require any PR submitted to k/website

@kacole2
Copy link
Contributor

kacole2 commented May 28, 2019 •
edited

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!

@kacole2
Copy link
Contributor

kacole2 commented May 30, 2019

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.

@smarterclayton
Copy link
Contributor Author

smarterclayton commented May 31, 2019 via email

@smarterclayton
Copy link
Contributor Author

smarterclayton commented May 31, 2019 via email

@kacole2
Copy link
Contributor

kacole2 commented Jul 5, 2019

This has graduated to stable and been implemented. Time to close

/milestone clear
/close

@k8s-ci-robot k8s-ci-robot removed this from the v1.15 milestone Jul 5, 2019
@k8s-ci-robot
Copy link
Contributor

@kacole2: Closing this issue.

In response to this:

This has graduated to stable and been implemented. Time to close

/milestone clear
/close

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.

@kacole2 kacole2 removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 5, 2019
@JimBugwadia JimBugwadia mentioned this issue Nov 3, 2020
Closed
@soltysh
Copy link
Contributor

soltysh commented Aug 19, 2021

The describe part of this enhancement isn't implemented, yet.

/re-open

@soltysh soltysh mentioned this issue Aug 19, 2021
Closed
@pacoxu
Copy link
Member

pacoxu commented Aug 19, 2021

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Aug 19, 2021
@k8s-ci-robot
Copy link
Contributor

@pacoxu: Reopened this issue.

In response to this:

/reopen

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.

@eddiezane eddiezane mentioned this issue Sep 15, 2021
Closed
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 17, 2021
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 17, 2021
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue.

In response to this:

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@soltysh soltysh

@smarterclayton smarterclayton

@juanvallejo juanvallejo

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests