Seeking clarification regarding usage and compatibility of Horizontal and Vertical Pod Autoscalers

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.6k stars 14.49k forks source link

Seeking clarification regarding usage and compatibility of Horizontal and Vertical Pod Autoscalers #42403

Open guettli opened 1 year ago

guettli commented 1 year ago

I missing a comparison to vertical Pod autoscaler.

I think these questions should be answered:

When to use hpa, when vpa?

Can you use hpa and vpa together?

utkarsh-singh1 commented 1 year ago

/language en /sig autoscaling

dipesh-rawat commented 1 year ago

/retitle Seeking clarification regarding usage and compatibility of Horizontal and Vertical Pod Autoscalers

dipesh-rawat commented 1 year ago

I can see in the kuberenete/autoscaler repository's VPA documentation (Vertical Pod Autoscaler - Known limitations), there's a known limitation mentioned:

Vertical Pod Autoscaler should not be used with the Horizontal Pod Autoscaler (HPA) on CPU or memory at this moment. However, you can use VPA with HPA on custom and external metrics.

sftim commented 1 year ago

/triage accepted

pegasas commented 1 year ago

/assign @pegasas

I will raise a PR for this but also seeking community suggestions for this issue.

@guettli

you could refer to official comments about https://github.com/kubernetes/design-proposals-archive/blob/main/autoscaling/vertical-pod-autoscaler.md#combining-vertical-and-horizontal-scaling

How about adding a character on docs/concept, and describing it shortly?

guettli commented 1 year ago

@pegasas this part you posted is good. I have not found it yet. I think it would be nice to have something like that in the docs.

pegasas commented 1 year ago

I would add a quarter like https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/ in this section.

k8s-triage-robot commented 3 months ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

k8s-triage-robot commented 2 weeks ago

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