Is your feature request related to a problem? Please describe.
Right now goldilocks does not support having multiples recommenders and always use the default where there are scenarios where could be helpful to allow defining which recommender to use.
We are running VPA within AKS with their managed module which does not support integrations with prometheus out of the box so we are running some extra recommender connected to our self-managed prometheus setup.
Describe the solution you'd like
Allowing the controller to define the name of the recommender you want to use within goldilocks would allow use to configure goldilocks to use a recommeder connected to prometheus.
Is your feature request related to a problem? Please describe.
Right now goldilocks does not support having multiples recommenders and always use the default where there are scenarios where could be helpful to allow defining which recommender to use.
We are running VPA within AKS with their managed module which does not support integrations with prometheus out of the box so we are running some extra recommender connected to our self-managed prometheus setup.
Describe the solution you'd like
Allowing the controller to define the name of the recommender you want to use within goldilocks would allow use to configure goldilocks to use a recommeder connected to prometheus.