Remove the deprecated --reconcile-cidr flag from kubelet

[luxas]

What this PR does / why we need it:

Removes the --reconcile-cidr flag that has been deprecated since v1.5

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

The `--reconcile-cidr` kubelet flag was removed since it had been deprecated since v1.5

@thockin

[k8s-reviewable]

This change is 

[k8s-ci-robot]

Jenkins Bazel Build failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot bazel test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GKE smoke e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot cvm gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCI GKE smoke e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCE etcd3 e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot gce etcd3 e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins Kubemark GCE e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot kubemark e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCE e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot cvm gce e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins CRI GCE Node e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot cri node e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCE Node e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot node e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCI GCE e2e failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gce e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins unit/integration failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot unit test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins verification failed for commit 359e735c47ae1b4e602791b105fa80dd83d234a7. Full PR test history.

The magic incantation to run this job again is @k8s-bot verify test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 39351, 39322)

[justinsb]

Do we have a policy for how long flags should stick around? If not, I'd suggest we should keep the flag as deprecated for 2 releases in future, not least because in this case the version that deprecated it was released only a few weeks ago.

[thockin]

The deprecation policy was merged, but jekyll is unhappy with some of the markdown (sigh), even though github itself renders just fine. I boldly assumed that since this was commented as "remove in 1.6" it had already been followed (I can't keep track of all the flags at this point :). https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/deprecation-policy.md says 6 months or 1 release, whichever is longer

…

On Tue, Jan 3, 2017 at 9:27 AM, Justin Santa Barbara < ***@***.***> wrote: Do we have a policy for how long flags should stick around? If not, I'd suggest we should keep the flag as deprecated for 2 releases in future, not least because in this case the version that deprecated it was released only a few weeks ago. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#39322 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVGDIor9bNXastTi3UtsQBYG7_rJEks5rOoUSgaJpZM4LYMNx> .

[brendandburns]

Yeah, this broke us due to the fact that it was deprecated too quickly. +1 for 6 months...