VPA Helm Chart

[techdragon]

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?

[dbirks]

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

[jkbschmid]

Any update on this issue? Is a Helm chart or support for any other deploy tool planned or generally desired?

[sebastien-prudhomme]

@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.

[fejta-bot]

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

[yashbhutwala]

/remove-lifecycle stale

[sudermanjr]

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.

FairwindsOps/charts#358

[mkjmkumar]

/remove-lifecycle stale

[fejta-bot]

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]

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

[techdragon]

/remove-lifecycle rotten

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[techdragon]

/remove-lifecycle stale

[k8s-triage-robot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[techdragon]

/remove-lifecycle stale

[jonkerj]

We (Equinix Managed Services NL) have rolled our own chart for VPA, and would love to submit it to be included upstream. What do the devs think about this?

[rabidscorpio]

@jonkerj Did anything happen with this? Did you submit your chart? I'd love to see something official adopted.

[jonkerj]

No, it went dead after my message on 7 Sep. If a PR is desired from the VPA devs, we'd be glad to submit ours.

We have mixed experience with putting a lot of effort into polishing something "internal" for PR/publication, so I'd like a confirmation from the devs before we put time into it (which we'd love to do).

[fredgate]

Maybe @bskiba has some answer.

[bskiba]

@jbartosik @kgolab for comment

[bskiba]

/assign @jbartosik

[jonkerj]

And it went silent again. Let's try and see if a PR that adds the chart can shed more light on this mystery 😉

[jonkerj]

Let me retract my previous offer. It seems our chart is not so rolled on our own as I claimed: we have a local fork of cowboysysops (@sebastien-prudhomme). So it is up to @sebastien-prudhomme (apparantly the best VPA chart currently out there) to include his work into this repo or not.

On the other hand: our offer still stands. Equinix is willing to submit a quality Helm chart, but I'd like confirmation from the project people before we put time and effort into this.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@borats: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[imageschool]

Still no confirmation..?!

[rileyai-dev]

@jbartosik @kgolab @bskiba A project already exists (https://github.com/cowboysysop/charts/tree/master/charts/vertical-pod-autoscaler) and AFAIK the owner is willing to contribute to its integration into your repo. @jonkerj is willing to submit a chart. All we need from the maintainers is an approval or at least an explanation...

It's been 2.5 years and still nothing! Can't we, at least, have a message from the team about this?

[jbartosik]

@rileyai-dev I'm happy to accept contributions but I don't have capacity to maintain Helm charts.

[martinnirtl]

Hi @sebastien-prudhomme!
i just read the history of this issue (including your comment), and wonder what's your stand on moving the chart to this repository and contribute to it here? i think, it would gain much more attraction here and the community is definitely waiting for a helm chart for vpa 😃

[mrclrchtr]

I landed here because I was looking for the easiest way to install VPA. Do you rather use https://github.com/cowboysysop/charts/tree/master/charts/vertical-pod-autoscaler or https://github.com/FairwindsOps/charts/tree/master/stable/vpa ?

It would be really great if there was an official chat.