Skip to content

Finish removing kubectl get all #124538

Closed as not planned
Closed as not planned
@ghost

Description

As has been extensively discussed on prior occasions (see kubernetes/kubectl#151), kubectl get all is not recommended, has been removed from documentation, and should be removed.

It appears that the primary reason this has not yet been completed is because the issue was filed against the kubernetes/kubectl issue tracker instead of kubernetes/kubernetes. At the request of the kubectl maintainers in kubernetes/kubectl#1584 (comment), the issue is being copied over to here.

The requested change is that kubectl get all is formally deprecated and eventually removed - or, fixed so that it does what it says it does.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions