cluster-api-provider-openstack icon indicating copy to clipboard operation
cluster-api-provider-openstack copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Autoscaling to zero

Open mkjpryor opened this issue 3 years ago • 18 comments

/kind feature

Describe the solution you'd like Auto-scaling to and from zero nodes has been implemented upstream - https://github.com/kubernetes/autoscaler/pull/4840.

We should make sure that we implement the provider side of this contract.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

mkjpryor avatar Aug 18 '22 13:08 mkjpryor

Adding a +1 because it would be a great feature!

braghettos avatar Sep 22 '22 14:09 braghettos

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 avatar Dec 21 '22 15:12 k8s-triage-robot

/remove-lifecycle stale

nikParasyr avatar Dec 21 '22 15:12 nikParasyr

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-triage-robot avatar Mar 21 '23 16:03 k8s-triage-robot

/remove-lifecycle stale

lukasmrtvy avatar Mar 21 '23 16:03 lukasmrtvy

https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20210310-opt-in-autoscaling-from-zero.md

mdbooth avatar Apr 24 '23 10:04 mdbooth

IIRC autoscaling from 0 already works, but it requires extra labels/annotations for the cluster-autoscaler. Implementing this would remove the need for these extra labels/annotations so it would be a bit easier for the user.

For me, this wouldnt be very high prio

nikParasyr avatar Apr 24 '23 10:04 nikParasyr

IIRC autoscaling from 0 already works, but it requires extra labels/annotations for the cluster-autoscaler. Implementing this would remove the need for these extra labels/annotations so it would be a bit easier for the user.

For me, this wouldnt be very high prio

This is correct I think. However I don't really want to have to query the flavor and add custom annotations to my machine deployment when a mechanism exists for the infrastructure provider to do this for me. Agree it isn't high, high priority but would certainly be good to implement the support since the hooks already exist in CAPI.

mkjpryor avatar Apr 25 '23 13:04 mkjpryor

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-triage-robot avatar Jan 19 '24 02:01 k8s-triage-robot

/remove-lifecycle stale

nikParasyr avatar Jan 19 '24 07:01 nikParasyr

@nikParasyr @mkjpryor Do either of you want to work on this, btw? Seems like a good feature.

mdbooth avatar Jan 30 '24 13:01 mdbooth

@mdbooth I dont have any time to work on this (unfortunately)

nikParasyr avatar Jan 31 '24 13:01 nikParasyr

/remove-lifecycle stale

EmilienM avatar Jan 31 '24 18:01 EmilienM

@mdbooth We think a customer might be about to ask for this. If they do then we will work on it.

mkjpryor avatar Feb 13 '24 20:02 mkjpryor

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-triage-robot avatar May 13 '24 20:05 k8s-triage-robot

/remove-lifecycle stale

EmilienM avatar May 13 '24 21:05 EmilienM