You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use cluster-proportional-autoscaler by managing our own manifests and configuration. Since it's published as an independent chert, we can consume it as a chart dependency and offload the manifest management to ti, see the repo for more details - https://github.com/kubernetes-sigs/cluster-proportional-autoscaler
One thing to consider is that it will change the way values are passed from the coredns chart to the cluster-proportional-autoscaler one so it will be a major version change with a potential for breaking changes. We should also document the change and recommendations on how to migrate from version 1.x.x -> 2.x.x
The text was updated successfully, but these errors were encountered:
We currently use
cluster-proportional-autoscaler
by managing our own manifests and configuration. Since it's published as an independent chert, we can consume it as a chart dependency and offload the manifest management to ti, see the repo for more details - https://github.com/kubernetes-sigs/cluster-proportional-autoscalerOne thing to consider is that it will change the way values are passed from the
coredns
chart to thecluster-proportional-autoscaler
one so it will be a major version change with a potential for breaking changes. We should also document the change and recommendations on how to migrate from version1.x.x
->2.x.x
The text was updated successfully, but these errors were encountered: