bump k8s deps to 1.27

[Huang-Wei]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

• bump go version to 1.20
• bump k8s version to 1.27
• bump controller-runtime to 0.15

Which issue(s) this PR fixes:

Fixes #606

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Bump go version to 1.20 and k8s deps to 1.27

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Huang-Wei

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:

• OWNERS [Huang-Wei]

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

[Huang-Wei]

@zwpaper you can take over if you have bandwidth.

Atop this PR, UT in pkg/controllers/elasticquota_controller_test.go failed. I haven't have cycle to look into it yet.

[zwpaper]

added a PR here Huang-Wei#1 to fix the failing test.

will do a full test later @Huang-Wei

[Huang-Wei]

added a PR here Huang-Wei#1 to fix the failing test.

Thanks a lot! I've merged that one in the fork repo, and push here.

I'm going to tweak the CI to use go 1.20, and then have the CI start here: kubernetes/test-infra#30235

[Huang-Wei]

/retest

[Huang-Wei]

CI failure:

--- FAIL: TestCapacityScheduling (34.38s)
    capacity_scheduling_test.go:59: The CRD is ready to serve
    capacity_scheduling_test.go:87: Init scheduler success
    --- FAIL: TestCapacityScheduling/cross-namespace_preemption (10.32s)
        capacity_scheduling_test.go:553: cross-namespace preemption Waiting expectedPods error: timed out waiting for the condition
    --- FAIL: TestCapacityScheduling/in-namespace_preemption (10.32s)
        capacity_scheduling_test.go:553: in-namespace preemption Waiting expectedPods error: timed out waiting for the condition
    --- FAIL: TestCapacityScheduling/cross-namespace_preemption_with_three_elasticquota (10.40s)

[Huang-Wei]

@zwpaper ^^ FYI

[zwpaper]

really strange, we did not change the logic related to the integration test, why is this keep failing and the origin tests work fine #610

it keeps report

E0804 15:56:02.187916   55780 framework.go:716] "Failed running RemovePod on PreFilter plugin" err="error reading \"PreFilterInterPodAffinity\" from cycleState: not found" plugin="InterPodAffinity" pod="ns2/t1-p5"

[zwpaper]

/test pull-scheduler-plugins-integration-test-master

[Huang-Wei]

it keeps report

E0804 15:56:02.187916   55780 framework.go:716] "Failed running RemovePod on PreFilter plugin" err="error reading > \"PreFilterInterPodAffinity\" from cycleState: not found" plugin="InterPodAffinity" pod="ns2/t1-p5"

@zwpaper I also spot this while debugging. I'm pretty sure it's a regression introduced in upstream v1.27. Let me file a fix in k/k.

[Huang-Wei]

@zwpaper to unblock bumping master to 1.27, I commented out those preemption tests. We can revert them once the upstream fix is available in the next v1.27 patch release. PTAL.

[zwpaper]

wow, I have tried and did not found that changes, let me have a look at the k/k issue and find out is there anything I can help.

/lgtm