🌱 Update to controller runtime 0.5.11

[randomvariable]

Signed-off-by: Naadir Jeewa jeewan@vmware.com

What this PR does / why we need it:

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 #

[randomvariable]

/assign @vincepri

[ncdc]

FWIW, the memory leak we fixed in controller-runtime only really occurs if you're dynamically adding a watch to a controller, and then you close/stop the cache (shared informers) associated with the that watch (e.g. when watching something from a workload cluster, not from the Manager's client/cache). It's fine to upgrade here, but it's not strictly required for CAPA from a memory leak perspective, I don't think.

[vincepri]

+1 to what Andy said, although we can merge this now if we want to ship CAPA with the fix earlier than CAPI

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

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

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

[CecileRobertMichon]

should we be doing this in CAPZ as well?

[randomvariable]

should we be doing this in CAPZ as well?

Won't hurt.

[detiber]

/lgtm