Don't call f.BeforeEach() again in ingress suite

[MrHohn]

What this PR does / why we need it: Calling f.BeforeEach() explicitly in ingress suite is causing test panics. See #56089.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes (hopefully) #56089

Special notes for your reviewer:

Release note:

NONE

[MrHohn]

Ref #56089 (comment).

[BenTheElder]

/priority failing-test

[BenTheElder]

This should also hopefully fix #56080

[MrHohn]

/assign @bowei @spiffxp

[BenTheElder]

This needs to be added to the milestone.
/kind bug

[abgworrall]

@bowei, can you status/approved-for-milestone this wearing your sig-network lead hat ?

[bowei]

@abgworrall -- I don't have the github perms...

[BenTheElder]

@abgworrall you're in the right team you should be able to /status approved-for-milestone
the last command here, the team here.

[abgworrall]

/status approved-for-milestone
I feel bad doing this on behalf of sig-network; but if bowei@ can't do that, then who can ...

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Pull Request Needs Attention

@MrHohn @bowei @caseydavenport @danwinship @spiffxp @kubernetes/sig-network-misc

Action required: During code slush, pull requests in the milestone should be in progress.
If this pull request is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight pull requests.

Note: This pull request is marked as priority/critical-urgent, and must be updated every 3 days during code slush.

Example update:

ACK.  In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required

Pull Request Labels

• sig/network: Pull Request will be escalated to these SIGs if needed.
• priority/critical-urgent: Never automatically move pull request out of a release milestone; continually escalate to contributor and SIG through all available channels.
• kind/bug: Fixes a bug discovered during the current release.

Help

• Additional instructions
• Commands for setting labels

[BenTheElder]

@abgworrall perhaps we should get @bowei on the milestone maintainers team? this seems fine though since you're just doing it on his behalf anyhow 🤷‍♂️

[bowei]

I am looking into getting said hat.

[bowei]

/lgtm

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, MrHohn

Associated issue: 56089

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

Needs approval from an approver in each of these OWNERS Files:

• test/e2e/network/OWNERS [MrHohn,bowei]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[caseydavenport]

fwiw, lgtm (and approved for milestone)

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[MrHohn]

/retest

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 56128, 56004, 56083, 55833, 56042). If you want to cherry-pick this change to another branch, please follow the instructions here.

[k8s-ci-robot]

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

Test name	Commit	Details	Rerun command
pull-kubernetes-bazel-test	11d283e	link	/test pull-kubernetes-bazel-test

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.