autoscaling
Here are 259 public repositories matching this topic...
-
Updated
Apr 29, 2021 - Go
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
-
Updated
May 3, 2021 - Go
-
Updated
Sep 28, 2020 - Smarty
-
Updated
Mar 25, 2021 - Java
-
Updated
Apr 28, 2020 - Python
-
Updated
May 1, 2021 - HCL
-
Updated
Mar 8, 2020 - Go
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.
-
Updated
Apr 14, 2021 - Go
-
Updated
Apr 6, 2021 - Perl
-
Updated
Apr 5, 2021 - Go
-
Updated
Nov 3, 2017 - Go
-
Updated
Apr 9, 2021 - Go
-
Updated
Feb 27, 2019 - Python
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
-
Updated
Apr 6, 2021 - Dockerfile
-
Updated
Jan 17, 2020 - Python
-
Updated
Apr 29, 2021 - Ruby
-
Updated
May 25, 2020 - Makefile
-
Updated
Apr 30, 2021 - HCL
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.
-
Updated
Jan 18, 2021 - Go
-
Updated
May 11, 2020 - Python
-
Updated
Jul 4, 2020 - HCL
-
Updated
Oct 29, 2020 - HCL
-
Updated
Jan 29, 2020 - Go
-
Updated
Dec 5, 2020 - JavaScript
Improve this page
Add a description, image, and links to the autoscaling topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the autoscaling topic, visit your repo's landing page and select "manage topics."
The resource name and the queue endpoint suffix should be configurable in triggers.
https://github.com/kedacore/keda/blob/57ffd4ee384db38f1169453cb16b31f00eacffa5/pkg/scalers/azure/azure_storage.go#L34-L64