**Context:** I have 60k items bogging down etcd, which I need to delete (most if not all of them). It's a managed k8s where I can't access etcd directly, so I'll have to go through the k8s API. All I need to delete the items are their names.

Sadly, the API doesn't seem to allow filtering what to return. I'd have expected something like `&responseFilter=metadata.name`.  
Without that, I need to perform a silly amount of requests with a tight `limit` and then filter out the names via `jq` locally. Otherwise, the API / etcd will just implode.

It this also the place to ask for `kubectl` enhacements? If so, why is there no `--limit` for kubectl? It's not too much of a deal to `kubectl proxy` and reach for the HTTP API. Yet, it's quite uncomfy (especially if you stumble over the api / apis difference).  
Of course, I'd also like to have that filtering available in `kubectl`.
Enhancement: allow to filter what fields to return from the API
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Enhancement: allow to filter what fields to return from the API
Issue date:

--- start body ---
**Context:** I have 60k items bogging down etcd, which I need to delete (most if not all of them). It's a managed k8s where I can't access etcd directly, so I'll have to go through the k8s API. All I need to delete the items are their names.

Sadly, the API doesn't seem to allow filtering what to return. I'd have expected something like `&responseFilter=metadata.name`.  
Without that, I need to perform a silly amount of requests with a tight `limit` and then filter out the names via `jq` locally. Otherwise, the API / etcd will just implode.

It this also the place to ask for `kubectl` enhacements? If so, why is there no `--limit` for kubectl? It's not too much of a deal to `kubectl proxy` and reach for the HTTP API. Yet, it's quite uncomfy (especially if you stumble over the api / apis difference).  
Of course, I'd also like to have that filtering available in `kubectl`.
--- end body ---
