Add subdomain entry to verify dns resolution

[mgdevstack]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug

/kind cleanup

/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
When a headless service is created which points to a pod having subdomain specified same as service name, DNS MUST be resolved to it's subdomain DNS entry as well as FQDN. So adding subdomain entry to verify DNS resolution.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

• default-subdomain.my-namespace.svc.cluster.local seems resolvable on Windows.
• Reference: tests: Splits hostname from DNS test #75591 (comment) , Promote DNS e2e verifying DNS resolution for hostname and subdomain #74982 (comment)
  Does this PR introduce a user-facing change?:

None

/sig testing
/sig windows
/area conformance
cc @BCLAU

[mgdevstack]

/test pull-kubernetes-e2e-aks-engine-azure-windows

[claudiubelu]

Hm, I don't think this test is included in the azure-windows job, as it only runs tests tagged with Conformance, NodeConformance, sig-windows, and a few other tags, none of which are included in this test.

[claudiubelu]

FWIW, the test passes on Windows with these changes: https://paste.ubuntu.com/p/G4V22KYybd/

[mgdevstack]

Thanks for confirming @BCLAU.
/test pull-kubernetes-e2e-gce
Awaiting for lgtm and approval so that this can be promoted to Conformance in #74982.

[johnbelamaric]

/test pull-kubernetes-e2e-aks-engine-azure-windows

[timothysc]

/assign @johnbelamaric

[mgdevstack]

@johnbelamaric, This e2e may not run in "pull-kubernetes-e2e-aks-engine-azure-windows" job based on @BCLAU comment #77503 (comment).

Could we review and approve this on priority so that #74982 can be closed.

[johnbelamaric]

If this test isn't even running then why is the job failing? I don't really want to merge it with the test failure - why is it failing? Is #77503 (comment) suggesting there is a change that will fix this?

[claudiubelu]

If this test isn't even running then why is the job failing? I don't really want to merge it with the test failure - why is it failing? Is #77503 (comment) suggesting there is a change that will fix this?

The job is failing in the cluster setup phase, it's not related to the test. We are looking into it. As mentioned, I've already tested these changes in my cluster and it was fine.

Since they use different networking solutions, it's probably a good idea to know if this change also works for @benmoss and @yujuhong .

[benmoss]

This applies to all clusters, not just Windows ones. Why is this Windows specific?

[johnbelamaric]

@benmoss it is not

/lgtm

[johnbelamaric]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnbelamaric, mgdevstack

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:

• test/e2e/network/OWNERS [johnbelamaric]

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

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[k8s-ci-robot]

@mgdevstack: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-aks-engine-azure-windows	831939b	link	/test pull-kubernetes-e2e-aks-engine-azure-windows

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.