Add e2e tests for kube-dns for comparison with CoreDNS

[rajansandeep]

This PR achieves the same goals as #7838

Ability to verify tests results of CoreDNS against kube-dns

CoreDNS is expected to replace kube-dns. See KEP : kubernetes/community#1956

One of the graduation criteria is to be able to:

Validate all e2e conformance and DNS related tests (xxx-kubernetes-e2e-gce, ci-kubernetes-e2e-gce-gci-ci-master and filtered by --ginkgo.skip=[Slow]|[Serial]|[Disruptive]|[Flaky]|[Feature:.+]) for CoreDNS. None of the tests successful with Kube-DNS should be failing with CoreDNS.

I propose here these 2 extra tests that will run always with kube-dns, whatever the default DNS service defined for K8s:

• the test for graduation criteria
• another test to validate the [Serial], [Slow] (but not Flaky). These tests includes some other DNS - specifics (like updating the DNS configuration by configMap).

/assign @fejta @MrHohn

[rajansandeep]

FYI @fturib

[fejta]

/approve

testgrid changes

[MrHohn]

Thanks!
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d3e6d9ee662986f9d6052a26a5d6284bd688e717

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fejta, MrHohn, rajansandeep

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:

• config/jobs/kubernetes/sig-network/OWNERS [MrHohn,fejta]
• testgrid/OWNERS [fejta]

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

[k8s-ci-robot]

@rajansandeep: Updated the job-config configmap using the following files:

• key sig-network-misc.yaml using file config/jobs/kubernetes/sig-network/sig-network-misc.yaml

In response to this:

This PR achieves the same goals as #7838

Ability to verify tests results of CoreDNS against kube-dns

CoreDNS is expected to replace kube-dns. See KEP : kubernetes/community#1956

One of the graduation criteria is to be able to:

Validate all e2e conformance and DNS related tests (xxx-kubernetes-e2e-gce, ci-kubernetes-e2e-gce-gci-ci-master and filtered by --ginkgo.skip=[Slow]|[Serial]|[Disruptive]|[Flaky]|[Feature:.+]) for CoreDNS. None of the tests successful with Kube-DNS should be failing with CoreDNS.

I propose here these 2 extra tests that will run always with kube-dns, whatever the default DNS service defined for K8s:

• the test for graduation criteria
• another test to validate the [Serial], [Slow] (but not Flaky). These tests includes some other DNS - specifics (like updating the DNS configuration by configMap).

/assign @fejta @MrHohn

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.