Upgrade to Controller Runtime v0.11.x

[sbueringer]

It would be great if we can use the next controller-runtime release (v0.11.x) in one of our next CAPI releases.

Anything else you would like to add:

I know it's early to already open the issue, but I think it's good to already have it so we're able to collect post-CR-upgrade tasks and also discuss if we want to already upgrade in CAPI v1.1.

Notes:

• as of today there is no CR v0.11 release
• CR main currently uses
  • Kubernetes 1.23.x (also doesn't have a release yet)
  • go-logr/logr v1.x (and thus enables kubernetes/klog v2.20+)

Post CR-upgrade tasks:

• Let's reconsider if we want to set the call depth when constructing the topologyReconcileLogger instead of during logging as introduced in 🌱 topologyReconcileLogger: print the correct log lines #5568
  • Note: With the new go-logr version that code won't compile anymore, so we have to do something when upgrading CR anyway.

First feedback in Slack suggests that we "probably want to use CR v0.11 in CAPI v1.1" and that it "probably makes sense to wait for a CR RC".

[Miscellaneous information that will assist in solving the issue.]

/kind feature
/area dependency

[vincepri]

/milestone v1.1
/kind release-blocking

[sbueringer]

Note: we're now on a pre-release version (a commit from main after beta 0) of CR. Let's keep this issue open until we use a v0.11.x CR release.