Add a method to TestContext to check if is IPv6

[aojea]

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:

This is a followup based on the following conversation

#81750 (comment)

to move the e2e ClusterIsIPv6() function to a method of TestContext

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This has to be merged after #82014

Does this PR introduce a user-facing change?:

NONE

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

[aojea]

/hold
/assign @pohly
/assign @neolit123

[neolit123]

@aojea
PTAL at the pull-kubernetes-bazel-test failures.

having this as a member function as @pohly recommended seems better to me.
(but whether TestContext being a public variable is sane, is another topic... :))
/approve

/assign @oomichi
for /test approval.

thanks.

[oomichi]

This seems to make the framework clean for me.

/lgtm
/approve
/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, neolit123, oomichi

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/framework/OWNERS [neolit123,oomichi]
• test/e2e/network/OWNERS [oomichi]

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

[oomichi]

/lgtm cancel

[oomichi]

Due to this change, one of unit tests related to e2elog is failed like

Ran 3 of 3 Specs in 0.022 seconds
FAIL! -- 0 Passed | 3 Failed | 0 Pending | 0 Skipped
--- FAIL: TestFailureOutput (0.04s)
    logger_test.go:104: 
        stack in 1
        Expected
            <string>: "...o:1364
            k8s...."
        to equal               |
            <string>: "...o:1369
            k8s...."
FAIL

We need to change test/e2e/framework/log/logger_test.go like

- stack: "\tutil.go:1369\nk8s.io/kubernetes/test/e2e/framework.ExpectNoError()\n\tutil.go:1363\nk8s.io/kubernetes/test/e2e/framework/log_test.glob..func1.4()\n\tlogger_test.go:49\nk8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync()\n\tlogger_test.go:65\n",
+ stack: "\tutil.go:1364\nk8s.io/kubernetes/test/e2e/framework.ExpectNoError()\n\tutil.go:1359\nk8s.io/kubernetes/test/e2e/framework/log_test.glob..func1.4()\n\tlogger_test.go:49\nk8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync()\n\tlogger_test.go:65\n",

(I faced the same problem on another PR #81685)

[aojea]

This has to be merged after #82014

:)

[oomichi]

Ah, got it :-)

[oomichi]

/lgtm

[aojea]

/retest
/hold cancel

The PR that fixed the unit test failures was merged

[aojea]

/test pull-kubernetes-conformance-kind-ipv6

[aojea]

/retest

[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.