Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable granularity for which controllers to run #5294

Open
enxebre opened this issue Nov 21, 2024 · 2 comments
Open

Enable granularity for which controllers to run #5294

enxebre opened this issue Nov 21, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@enxebre
Copy link
Member

enxebre commented Nov 21, 2024

/kind feature

Describe the solution you'd like
As a cluster service provider managing a multi-tenant environment I would like to setup my capi controllers to watch only well known targeted resources and do not run unnecessary controllers. E.g If I'm targeting aro/aks clusters I don't need to run the AzureMachine or the AzureCluster controllers or if I'm using AzureMachine with externally managed infra I don't need ASOAPI

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • cluster-api-provider-azure version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 21, 2024
@damdo
Copy link
Member

damdo commented Nov 21, 2024

/cc @nojnhuh @mboersma @jackfrancis

@bryan-cox
Copy link
Contributor

This helps some with this - #5099

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Todo
Development

No branches or pull requests

4 participants