autoscaling

Proposal

As disscuseed on kedacore/keda#2765 (comment), we should unify the functions for Status & Conditions handling. Referencing controller related stuff here is suboptimal.

There are two locations with similar functions:
https://github.com/kedacore/keda/blob/9f0ee58fc6839d74636e1ec6883fe21d82617ea3/controllers/keda/util/status.go#L30-L63
https://g

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

Currently craned only read recommendation config when craned is starting, if you change the recommendation config, craned will also use old configuration.

It would be better to aware the change for configmap and reload it in memory.

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:

1. Easy to debug.
2. 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)