Delete with empty name results in deletecollection

[jpbetz]

What happened (please include outputs or screenshots):

According to kubernetes/kubernetes#127746, if delete is called with an empty name, the client will not fail but instead call delete on the collection resource and delete the entire collection of resources.

What you expected to happen:

Delete either performs the delete of a single resource, or fails.

How to reproduce it (as minimally and precisely as possible):

Call delete, but provide an empty name.

cc @zhifei92

[roycaihw]

The delete method compose the request to something like api/v1/namespaces/{namespace}/pods/{name} and when name is empty, it becomes api/v1/namespaces/{namespace}/pods, which by Kubernetes definition will delete all resources in the namespace / cluster.

This was also reported in #2209

I think at this point it will be hard to change this behavior, because we don't know how many users may already depend on this behavior.

[jpbetz]

What would the client code from python look like to make this call? Is there already a separate deletecollection call?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten