Closed deepakzac closed 7 months ago
/area vertical-pod-autoscaler
Hey @deepakzac, thanks for the detailed description!
I can see that you're using a CRD to manage your etcd cluster. Similar to the Horizontal Pod Autoscaler, the VPA has some requirements for autoscaling custom resources, namely it needs the /scale
subresource.
Looking at the CRD's name, I'm wondering if you are using the CoreOS etcd operator? Given that the project is archived for a few years already, this seems not like a good idea. You might want to switch to an alternative, which hopefully also supports the /scale
subresource, such as https://github.com/gardener/etcd-druid or find a different way to provide a managed etcd solution.
I'm closing this for now, feel free to re-open with additional information if I'm getting things wrong here!
/remove-kind bug /kind support /close
@voelzmo: Closing this issue.
@voelzmo Thank you for the quick response and the pointer to the FAQ. I missed that. Makes sense. And yes, we are using the operator from CoreOS.
Which component are you using?:
vertical-pod-autoscaler What version of the component are you using?: VPA version 1.0
Component version:
What k8s version are you using (
kubectl version
)?:kubectl version
OutputWhat environment is this in?: On Prem
What did you expect to happen?: VPA is successfully created and provides recommendation for etcd-cluster service
What happened instead?: See the below error
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: