It would be very useful to have a Helm Chart for deploying the Vertical Pod Autoscaler. At the moment its one of the few parts I cant deploy in any kind of idempotent/config management toolchain ( other than using shell execution of course 馃槃)
If there is a recommended one it should be documented somewhere, if not, could someone more familiar with the install scripting look at if there are any blockers to making a helm chart?
techdragon
All 10 comments
I've noticed a chart by @sebastien-prudhomme that he may want to contribute:
https://github.com/cowboysysop/charts/tree/master/charts/vertical-pod-autoscaler
dbirks
on 22 Apr 2020
Any update on this issue? Is a Helm chart or support for any other deploy tool planned or generally desired?
jkbschmid
on 25 May 2020
@jkbschmid i'm the author of the above chart.
If you look at the cluster-autoscaler Helm chart, it's maintained by the Helm community not the Kubernetes organization.
My feeling is that Kubernetes developpers don't want to take care of application packaging. They just provide raw YAML the same way some open source products just provide source code without DEB or RPM package.
I can understand it because some people, like me, prefer Helm, other people prefer Kustomize and so on.
sebastien-prudhomme
on 26 May 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 24 Aug 2020
/remove-lifecycle stale
yashbhutwala
on 24 Aug 2020
Found this issue after I created my own chart today. Seems very similar to the other one mentioned here. We will continue to maintain this one for now since it is a component needed by another tool of ours.
sudermanjr
on 8 Sep 2020
/remove-lifecycle stale
mkjmkumar
on 23 Sep 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 22 Dec 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 21 Jan 2021
/remove-lifecycle rotten
techdragon
on 3 Feb 2021
Related issues
hprotzek
路
5Comments
tjliupeng
路
6Comments
mboersma
路
6Comments
pkelleratwork
路
5Comments
losipiuk
路
7Comments
Most helpful comment
@jkbschmid i'm the author of the above chart.
If you look at the cluster-autoscaler Helm chart, it's maintained by the Helm community not the Kubernetes organization.
My feeling is that Kubernetes developpers don't want to take care of application packaging. They just provide raw YAML the same way some open source products just provide source code without DEB or RPM package.
I can understand it because some people, like me, prefer Helm, other people prefer Kustomize and so on.