Handle cluster-autoscaler Deployment in generic controlplane mutator #6047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/area auto-scaling
/kind enhancement
What this PR does / why we need it:
When our forked cluster-autoscaler adopts a version of the upstream cluster-autoscaler that contains kubernetes/autoscaler#4539 (or any of its backports) we have to specify the CSI feature gates for the cluster-autoscaler Deployment. As the CSI feature gates are different for the different cloud providers we have to enhance the generic controlplane mutator and allow provider extensions to mutate the cluster-autoscaler Deployment in order to add the CSI feature gates.
Which issue(s) this PR fixes:
Part of #5064
Release note: