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

Please finish removing 'kubectl get all' #1591

Closed
raxod502-plaid opened this issue Apr 25, 2024 · 5 comments
Closed

Please finish removing 'kubectl get all' #1591

raxod502-plaid opened this issue Apr 25, 2024 · 5 comments
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@raxod502-plaid
Copy link

This is a follow-on to the issue #151 which was incorrectly closed even though nothing was done to resolve it. #1584 requested that the original issue be reopened but a maintainer instead requested that a third issue be opened instead to make it clear that the remaining unaddressed work that would be needed to close the original issue is to finish removing kubectl get all if it is never going to be fixed to work properly.

Concerns were raised in the original thread about why it would be difficult to deprecate kubectl get all, and it was explained why those concerns didn't make sense, but no response was given and the issue was closed without explanation. Hence this issue.

See #1584 (comment) for where to pick up discussion.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 25, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@ardaguclu
Copy link
Member

This issue is duplicate of #1584 and #1584 is already open. I'm not sure why this one exists.
/close

@k8s-ci-robot
Copy link
Contributor

@ardaguclu: Closing this issue.

In response to this:

This issue is duplicate of #1584 and #1584 is already open. I'm not sure why this one exists.
/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.

@sftim
Copy link
Contributor

sftim commented Apr 25, 2024

/close not-planned
/triage duplicate

@k8s-ci-robot k8s-ci-robot added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Apr 25, 2024
@raxod502-plaid
Copy link
Author

This issue is duplicate of #1584 and #1584 is already open. I'm not sure why this one exists.

The reason this issue exists, as mentioned in the issue text, is because @sftim specifically requested that a duplicate be filed, see the comment at #1584 (comment). I agree it's a duplicate and would have preferred not to file it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

4 participants