Allow adding extra rules to the Role / ClusterRole template of the Cluster AutoScaler Helm chart #7680
Description
Which component are you using?:
/area cluster-autoscaler
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
I am using ClusterAPI + Cluster AutoScaler, and would like to use the opt-in support for scaling from zero provided by the AWS Infrastructure Provider (can be any other Infrastructure Provider as well, like : Hetzner / GCP / Azure).
This requires me to add the Infrastructure Machine template types to the Role / ClusterRole associated with the Cluster AutoScaler deployment (refer here).
The Cluster AutoScaler Helm chart doesn't allow me to add extra rules to the Role / ClusterRole.
Describe the solution you'd like.:
I would like the Helm chart to have some parameter, using which I can add whatever additional rules to the Role / ClusterRole
Describe any alternative solutions you've considered.:
If you don't agree with the above solution, then we can have specific rules for each Infrastructure Provider hardcoded in the Role / ClusterRole template. I can bring the extra rules for an Infrastructure Provider into effect using some parameter.
Additional context.:
NA
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Participants
Activity
k8s-triage-robot commentedon Apr 9, 2025
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot commentedon May 9, 2025
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
k8s-triage-robot commentedon Jun 8, 2025
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot commentedon Jun 8, 2025
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.