autoscaling

Proposal

Need to add support for X-Scope-OrgID header as part of the query to a multi tenant cortex (prometheus metrics), since it's not possible to get a response without it when multi tenancy is enabled.

Use-Case

We're using scalers from type prometheus, and recently moved to a multi tenant cortex to serve metrics from multiple different prometheus instances in different clusters.

Is your feature request related to a problem? Please describe.

Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.

Describe the solution you'd like

Check for changes in nodegroup config before each run. If safe to do so, run with the new config.

*Describe alternatives you've considered

Describe the feature

Current Node Resource Controller update Kubernetes node ext resource with the predicted idle resource, all idle resources will be reallocated as ext resource which can be used by lower priority pods, especially for offline job, however this would leads the node resource to be exhausted, thus some of them would be evicted during the the execution.
So the request is to make

Description

With the changes introduced in #227, Noma API calls for job scaling operations were updated to permit stale reads. We should update the remainder of Nomad API calls for consistency and decreased load on the Nomad Servers.

We have often see developer telling us the problems going on with WPA and then the first way to debug the issue is by going through WPA kubernetes logs for the queue to find what is going on. We should logs events for all the important thing that goes on with the WPA object.

Reasons:

Easy to debug.
Developer who does have access to wpa logs but has access to their WPA object can tro

The interceptor should be able to route requests for the same host to different services based on the request path.

Use-Case

When using an ingress controller, you can create Ingress objects that route different requests for the same host to different backend services, depending on the path portion of the request. This can be done by within a single Ingress object or across multiple of

The port limit constant (10) should be lifted into a constant and reused in our ports value validation, in the k8s get-port-range function, and anywhere else it is used.

See twosigma/waiter#1193 (comment)

Feb	MAR	Apr
	10
2021	2022	2023

autoscaling

Here are 303 public repositories matching this topic...

kedacore / keda

Proposal

Use-Case

cloudutil / AutoSpotting

atlassian / escalator

zalando-incubator / kube-metrics-adapter

Thakurvaibhav / k8s

learnk8s / spring-boot-k8s-hpa

gocrane / crane

Describe the feature

terraform-aws-modules / terraform-aws-autoscaling

jthomperoo / custom-pod-autoscaler

sebdah / aws-ec2-assign-elastic-ip

jthomperoo / predictive-horizontal-pod-autoscaler

elsevier-core-engineering / replicator

jrasell / sherpa

pplu / aws-sdk-perl

DataDog / watermarkpodautoscaler

practo / k8s-worker-pod-autoscaler

Reasons:

openfresh / ecs-formation

stefanprodan / istio-hpa

kedacore / http-add-on

Use-Case

hjacobs / kube-aws-autoscaler

cloudposse / terraform-aws-ec2-autoscale-group

magenx / Magento-2-aws-cluster-terraform

sensu-plugins / sensu-plugins-aws

aws / aws-auto-scaling-custom-resource

twosigma / waiter

openshift-examples / web

valencenet / valence-manifests

underarmour / libra

realabbas / scaling-nodejs

structurely / ecs-autoscale

Improve this page

Add this topic to your repo