Promote ExpandedDNSConfig feature to beta stage

[gjkim42]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This adds an e2e test for ExpandedDNSConfig and promotes KEP 2595 (Expanded DNS Configuration) to the beta stage.

ref: kubernetes/enhancements#2884

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

The ExpandedDNSConfig feature has graduated to beta and is enabled by default. Note that this feature requires container runtime support.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2595-expanded-dns-config

[k8s-ci-robot]

@gjkim42: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[gjkim42]

/retest

[sftim]

I wouldn't list container runtime support in the release note: we try not to pick favorites, and I'd rather not try to produce a definitive list of container runtimes that include the necessary support.

If we do add a definitive list, we need to make sure that it remains in alphabetical order.

We don't have project guidance on 3rd party software mentions in release notes, but https://github.com/cncf/foundation/blob/main/website-guidelines.md is along similar lines.

It's OK to publish a blog article for the release where this graduates to beta, and mention compatible runtime examples in that blog article.

• blog articles are authors' opinions, modulated by project-wide theme and style constraints
• if you've made, or someone else has made, a reasonable effort to write a balanced blog article, we don't mind if you omitted some obscure runtime that is also compatible, and it's easier to retrospectively add a note to such an article if you ever want to.

[aojea]

@gjkim42 did you forget to remove the WIP from the title or is still something missing?

/lgtm

/assign @thockin
for approval

[gjkim42]

I wouldn't list container runtime support in the release note: we try not to pick favorites, and I'd rather not try to produce a definitive list of container runtimes that include the necessary support.

removed the container runtime list from the release note.

And removed WIP.

[thockin]

Thanks!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gjkim42, 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:

• pkg/features/OWNERS [thockin]
• test/e2e/network/OWNERS [thockin]

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