This issue is to track upgrading from v0.6.1 controller runtime to v0.7.2+. This brings on a lot of changes to Controller Runtime and is closer to the release we use for the rest of CAPN.
This will start the move towards more consistent usage of contexts throughout all the reconcilers and syncer and align us for easier integration.
In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/59#issuecomment-852605323):
>/close
>
>This work was done in #70
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
This issue is to track upgrading from
v0.6.1
controller runtime tov0.7.2+
. This brings on a lot of changes to Controller Runtime and is closer to the release we use for the rest of CAPN.This will start the move towards more consistent usage of
contexts
throughout all the reconcilers and syncer and align us for easier integration.