Enable CoreDNS as default for kube-up deployments

[fturib]

What this PR does / why we need it:
Enable CoreDNS as default (for kube-up installations)
It will allow to run CI tests to prepare graduation criteria for CoreDNS as Default

see : KEP - https://github.com/kubernetes/community/blob/master/keps/sig-network/0012-20180518-coredns-default-proposal.md
see also : kubernetes/enhancements#566

NOTE for release : I guess that CoreDNS as default server for k8s needs a longer description. This specific PR is to ensure we validate all e2e.

Make CoreDNS be the default DNS server in kube-up (instead of kube-dns formerly). 
It is still possible to deploy kube-dns by setting CLUSTER_DNS_CORE_DNS=false.

[fturib]

@rajansandeep : I spend long time to check the failing e2e tests for the other PR. And I guess there cases when the e2e pull-kubernetes-gce ends in cored dumped and then timeout.
That does not explain all the issue .. but I would like to test with another PR.

Could you set the flat "ok-to-test" ? Thanks!
related PR is here : #62147

And, for sure, the I cannot reproduce on similar deployment e2e on GCE ... :)
Here is what I get on test on a private test on GCE:

running:

cd $GOPATH/src/github.com/kubernetes/kubernetes
kubetest --dump=/tmp/whatever/_artifacts --gcp-service-account=/home/admin/k8s-coredns-integration-8b248dc238e6.json --up --test --provider=gce --gcp-node-image=gci --gcp-zone=us-central1-f --ginkgo-parallel=30 --runtime-config=batch/v2alpha1=true,admissionregistration.k8s.io/v1alpha1=true --timeout=65m --test_args="--ginkgo.skip=\\[Slow\\]|\\[Serial\\]|\\[Disruptive\\]|\\[Flaky\\]|\\[Feature:.+\\] --minStartupPods=8"

result:

Ran 486 of 1032 Specs in 1215.969 seconds
SUCCESS! -- 486 Passed | 0 Failed | 0 Pending | 546 Skipped 

[rajansandeep]

/ok-to-test

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

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.

[fturib]

With consensus on the way to resolve this issue : kubernetes/dns#254

Adding port remapping to 10053.
That will avoid to deal with super-admin privileges and therefore with PodSecurityPolicies.
This mapping was the only point that needed privileges

[fturib]

/unlabel area/apiserver

[fturib]

I mad a mistaking in build the push ... and therefore for a few time had a lot of code. and the Bot added a lot of labels.
I change the commit and have now the correct change. However the labels are not going away ...

@rajansandeep : do you have a way to remove the unecessary labels : all "area/..", "sig/xx"
And then will add the "sig/network". ?

[thockin]

@kubernetes/sig-contributor-experience-bugs

Hey contribex folks - Am I not able to LGTM something without approving? I see those two statements as very orthogonal.

[dims]

@thockin looking at the following

• Add option to toggle if /lgtm also means /approve test-infra#7504
• https://groups.google.com/forum/#!msg/kubernetes-dev/PJJxV9roXI8/aIeHQdKoBwAJ
• kubernetes/test-infra@9a805e3

I can flip the config to set lgtm_acts_as_approve: false for k/k

[fturib]

/test pull-kubernetes-e2e-kops-aws

[fturib]

/retest

[fturib]

/retest

[fturib]

@thockin : this PR is ready.
It enables CoreDNS as the default DNS Service when Kubernetes is deplyed with Kube-up.

This PR does not depend to any release of CoreDNS and can be applied immediately

NOTE: I think it would be good to merge asap, so we can evaluate impact on ALL the e2e tests that uses kube-up to deploy a cluster for test.

I would not expect issue ... but who knows ?

[rajansandeep]

@kubernetes/sig-network-pr-reviews @thockin
This PR requires the milestone tags and lgtm to merge.

[neolit123]

/remove-kind bug
/kind feature

[justaugustus]

/milestone v1.12

[justaugustus]

/test pull-kubernetes-e2e-gke

[thockin]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fturib, thockin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cluster/gce/OWNERS [thockin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 67745, 67432, 67569, 67825, 67943). If you want to cherry-pick this change to another branch, please follow the instructions here: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md.