✨ upgrade to k8s 0.27.1

[mythi]

This PR moves k8s dependencies to 0.27.1 and reworks things to make the tests/linter happy.

k8s.io/apimachinery deprecated legacy Poll methods and this
triggers golangi-lint staticheck errors.

Rework all the poll logic to move to the preferred methods.

Details: kubernetes/apimachinery@831cf05

Additionally, NamespacedName type now implements MarshalLog() which
replaces the functionality in kube_helpers.go. See k/k #117238..

[k8s-ci-robot]

Welcome @mythi!

It looks like this is your first PR to kubernetes-sigs/controller-runtime 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/controller-runtime has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mythi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[howardjohn]

I have an alternative PR that makes controller-runtime support 1.27 and 1.26 concurrently so projects do not need to serialize updates: #2223

I am also fine with this, just presenting an option. I would like to see some support for 1.27 merged ideally, though.

[mythi]

I have an alternative PR that makes controller-runtime support 1.27 and 1.26 concurrently so projects do not need to serialize updates: #2223

I am also fine with this, just presenting an option. I would like to see some support for 1.27 merged ideally, though.

I'm totally fine with the proposed alternative. My goal (this PR) was also to just get to 1.27...

[mythi]

I have an alternative PR that makes controller-runtime support 1.27 and 1.26 concurrently so projects do not need to serialize updates: #2223
I am also fine with this, just presenting an option. I would like to see some support for 1.27 merged ideally, though.

I'm totally fine with the proposed alternative. My goal (this PR) was also to just get to 1.27...

Rebased since #2223 is now merged.

[mythi]

@alvaroaleman @vincepri could I get ok-to-test to see tests are passing. make test was passing for me locally

[alvaroaleman]

/ok-to-test

[sbueringer]

lgtm from my side pending 0.27.2 and resolution of #2189 (comment) (let's wait for feedback there)

[sbueringer]

@mythi Thank you very much for all your work on this!!

/lgtm

[sbueringer]

/assign @vincepri @alvaroaleman

[alvaroaleman]

Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alvaroaleman, mythi

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

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

[vincepri]

/hold cancel

[sbueringer]

Please note that we are still waiting for v0.27.2 with the v0.15 release.

Follow-up issue: #2297

[mythi]

@mythi Thank you very much for all your work on this!!

no problem. Even if this PR turned out to be WAY bigger task than I originally planned, I don't mind since I believe it gives a good learning for the future as well: it's probably good to start pulling/testing k8s release candidates to ensure all is good ahead of the release.