autoscaler icon indicating copy to clipboard operation
autoscaler copied to clipboard

Support running a cluster-autoscaler in a multi-cloud Kubernetes Cluster

Open jaredallard opened this issue 1 year ago • 5 comments

Which component are you using?: cluster-autoscaler

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

When running a cluster with multiple clouds, e.g. gcp and self-hosted, you cannot run cluster-autoscaler because it gets stuck on providerID being not set (or not a GCE value) (https://github.com/kubernetes/autoscaler/issues/4242)

Describe the solution you'd like.: A flag / or some other mechanism for picking a single cloud for a cluster-autoscaler instance to "look" for. This seems like the easiest way to support this since one could run a cluster-autoscaler per cloud.

I'd imagine that there'd also need to be support for ignoring certain workloads/limiting them to each cloud if that were the case.

Describe any alternative solutions you've considered.: I'm not aware of any other solutions.

Additional context.: n/a

jaredallard avatar Dec 03 '22 22:12 jaredallard

From "The modern mode, 'use strict'" chapter:

image

Alexandre887 avatar Nov 04 '23 00:11 Alexandre887

@Alexandre887 Ok understood, so I guess its a good practice to use the following, what do you think? "use strict" window.onerror() process.on() in Node env.

tausiq2003 avatar Nov 04 '23 03:11 tausiq2003