Value Statement

As a cluster service provider managing a multi-tenant environment I would like to setup my capA controllers to watch only well known targeted resources and do not run unnecessary controllers. E.g If I'm targeting rosa/eks clusters I don't need to run the AWSmachine or the AWSCluster controllers

https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/5124

Ref for Feature gates: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/feature/feature.go

Ref for Feature gate controller check: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/main.go#L128

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.