Configure controllers to watch ASO resources and queue reconcile requests for the appropriate CAPZ resources

[nojnhuh]

/kind cleanup

What needs cleanup:
Currently, CAPZ doesn't use the "watch" feature of Kubernetes clients to react to changes to ASO resources asynchronously. Instead, CAPZ has been liberally returning reconciliation Results with a defined RequeueAfter to effectively poll for status. These RequeueAfter values introduce some potential dead time where an ASO resource has been updated but the CAPZ controller is still waiting until RequeueAfter to re-reconcile the CAPZ resource. This extra time could be cut down with a watch set up on the ASO resources.

Describe the solution you'd like
Configure each controller in its SetupWithManager to watch the appropriate ASO resources and enqueue reconcile requests. #4340 would make this fairly straightforward with the Owns() method of the controller builder.

Anything else you would like to add:
One open question: Should CAPZ watch BYO ASO resources and queue requests based on changes to them?

[dtzar]

Sounds like this would help with at least the time until the resources are cleaned up re: #4570

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dtzar]

/remove-lifecycle stale