-
Notifications
You must be signed in to change notification settings - Fork 923
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
Comments
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 The 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: 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. |
/close not-planned |
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. |
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.
The text was updated successfully, but these errors were encountered: