Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm chart for VPA #5369

Open
sathieu opened this issue Dec 14, 2022 · 17 comments
Open

Helm chart for VPA #5369

sathieu opened this issue Dec 14, 2022 · 17 comments
Labels
area/vertical-pod-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@sathieu
Copy link

sathieu commented Dec 14, 2022

Which component are you using?:

VPA (Vertical Pod Autoscaler)

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

Easily deploy VPA.

Describe the solution you'd like.:

An Helm chart.

@sathieu sathieu added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 14, 2022
@brsolomon-deloitte
Copy link

brsolomon-deloitte commented Dec 15, 2022

Duplicate of #3068, which went completely unanswered by the maintainers.

We use https://artifacthub.io/packages/helm/cowboysysop/vertical-pod-autoscaler, which is actively maintained and a good-quality chart, though it is third-party.

@sathieu
Copy link
Author

sathieu commented Dec 15, 2022

Thanks @brsolomon-deloitte

@gczarnocki
Copy link

@Shubham82
Copy link
Contributor

Hi @jbartosik, your thoughts on this?

@jbartosik
Copy link
Collaborator

I'm happy to accept contributions but I won't be able to maintain Helm charts

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2023
@Shubham82
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 1, 2023
@AhmedGrati
Copy link

Hi @sebastien-prudhomme, wondering what's your stand on moving the chart to this repository and contributing to it here.

@sebastien-prudhomme
Copy link

Hi @AhmedGrati I try to maintain all the charts I wrote the same way. It will be hard for me to continue the maintenance here while keeping the same consistency. But I can discontinue my chart if someone want to take inspiration from it to build a new one.

The main difference I see with the other Helm chart available in this repo is the fact that I'm using Bitnami common subchart and Bitnami tool to generate the documentation.

@AhmedGrati
Copy link

Yeah, I asked you because I want to be inspired by your chart to build a new one here. Therefore, I wanted to check whether you have plans to maintain a new chart here or not before I start working on it.

@sudermanjr
Copy link

I would be willing to consider donating / moving our chart to this repository if it would be a positive impact for the community. https://artifacthub.io/packages/helm/fairwinds-stable/vpa

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@Shubham82
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 31, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2024
@nick-oconnor
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2024
@calebAtIspot
Copy link

Can we remove the stale bot from this issue please? It's not a bug that might be randomly fixed by a refactor, and it's already a popular feature request with +18 votes.

@Shubham82
Copy link
Contributor

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vertical-pod-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests