Closed raxod502-plaid closed 2 months ago
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.
This issue is duplicate of https://github.com/kubernetes/kubectl/issues/1584 and https://github.com/kubernetes/kubectl/issues/1584 is already open. I'm not sure why this one exists. /close
@ardaguclu: Closing this issue.
/close not-planned /triage duplicate
This issue is duplicate of https://github.com/kubernetes/kubectl/issues/1584 and https://github.com/kubernetes/kubectl/issues/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 https://github.com/kubernetes/kubectl/issues/1584#issuecomment-2073405467. I agree it's a duplicate and would have preferred not to file it.
This is a follow-on to the issue https://github.com/kubernetes/kubectl/issues/151 which was incorrectly closed even though nothing was done to resolve it. https://github.com/kubernetes/kubectl/issues/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 https://github.com/kubernetes/kubectl/issues/1584#issuecomment-2049957900 for where to pick up discussion.