orphan when kubectl delete --cascade=false

[deads2k]

The default for new objects is to propagate deletes (use GC) when no deleteoptions are passed. In addition, the vast majority of kube objects use this default. Only a few controllers resources (sts, rc, deploy, jobs, rs) orphan by default. This means that when you do kubectl delete sa/foo --cascade=false you do not orphan. That doesn't fulfill the intent of the command. This explicitly orphans when --cascade=false so we don't use GC.

@fabianofranz
@jwforres I liked this easter egg :)

@kubernetes/sig-cli-bugs we should backport this to 1.6

[k8s-reviewable]

This change is 

[0xmichalis]

/lgtm
/release-note-none

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, kargakis

Needs approval from an approver in each of these OWNERS Files:

• pkg/kubectl/OWNERS [deads2k]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-ci-robot]

@deads2k: The following test(s) failed:

Test name	Commit	Details	Rerun command
pull-kubernetes-federation-e2e-gce	e91716a	link	@k8s-bot pull-kubernetes-federation-e2e-gce test this

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[k8s-github-robot]

Automatic merge from submit-queue

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.