Repository navigation
Support separate configuration for autoscaler selector and labels #179
Description
In the templates for both the deployment and deployment-autoscaler, the customLabels and deployment.selector values are re-used. This makes it difficult to use helm and configure these objects separately, as the shared configuration will cause accidental selection of pods that are not part of the other deployment since these values are shared. These should be separated so that the labels for the autoscaler have separate values
Activity
[-]Support separate configuration for autoscaler selector[/-][+]Support separate configuration for autoscaler selector and labels[/+]sage-s11 commentedon Aug 27, 2026
I'd like to take this.
Plan: add autoscaler.inheritCustomLabels (default true), autoscaler.customLabels, autoscaler.podLabels, and autoscaler.selector so the autoscaler can be labeled/selected independently. Defaults stay backward compatible.