Promote KEP-2681 to beta in 1.29

[wzshiming]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Test fix by #121429

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Promote PodHostIPs condition to beta.

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

- [KEP]: https://github.com/kubernetes/enhancements/issues/2681
- [Usage]: <link>
- [Other doc]:

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

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.

[wzshiming]

/cc @aojea @thockin

[wzshiming]

https://kubernetes.slack.com/archives/C0BP8PW9G/p1698148744408089?thread_ts=1698045918.027889&cid=C0BP8PW9G

@aojea

Do I add tests to test/e2e/network/dual_stack.go in this PR or after this PR landed?

#121479

[dims]

/milestone v1.29

Do we want to do this @thockin @aojea ? is it ready ?

[hailkomputer]

Hello, bug triage team lead here. I want to check the status and remind that the the code freeze is starting 01:00 UTC Wednesday 1st November 2023 / 18:00 PDT Tuesday 31st October 2023, as we want to ensure that each PR has a chance to be merged.
Are we still targeting the 1.29 release?

[pacoxu]

/priority important-soon

#121429 changed the case to run serialized as the node e2e tried to restart kuebelet. And it will skip if the FG is not enabled.(The current node e2e doesn't support it well, so the current workaround is just to check the default one. THere is a WIP PR #120139 on this)

[wzshiming]

Test has been updated in #121429, #121479 and this PR is ready to be merge.

[aojea]

/test pull-kubernetes-cos-cgroupv1-containerd-node-e2e-features
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-features
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial

[pacoxu]

/test pull-kubernetes-e2e-kind-alpha-beta-features
/test pull-kubernetes-e2e-kind-alpha-features
/test pull-kubernetes-e2e-kind-beta-features

[thockin]

I have not had time to re-review this, and as long as tests are failing it's stuck.

[aojea]

I have not had time to re-review this, and as long as tests are failing it's stuck.

@thockin tests should be good now, this is good to go

[thockin]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 7e50bfbb1bf7b9e6dbcece7bc759db16f2cd290d

[thockin]

/retest
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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]

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]

@wzshiming: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-kind-beta-features	12a972c	link	false	/test pull-kubernetes-e2e-kind-beta-features
pull-kubernetes-e2e-kind-alpha-beta-features	12a972c	link	false	/test pull-kubernetes-e2e-kind-alpha-beta-features
pull-kubernetes-e2e-kind-alpha-features	12a972c	link	false	/test pull-kubernetes-e2e-kind-alpha-features

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.