You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 24, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: README.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ The autoscaler consists of a simple main loop which calls the ``autoscale`` func
49
49
The main loop keeps no state (like history), all input for the ``autoscale`` function comes from either static configuration or the Kubernetes API server.
50
50
The ``autoscale`` function performs the following task:
51
51
52
-
* retrieve the list of all nodes from the Kubernetes API and group them by Auto Scaling Group (ASG) and Availability Zone (AZ)
52
+
* retrieve the list of all (worker) nodes from the Kubernetes API and group them by Auto Scaling Group (ASG) and Availability Zone (AZ)
53
53
* retrieve the list of all pods from the Kubernetes API
54
54
* calculate the current resource "usage" for every ASG and AZ by summing up all pod resource requests (CPU, memory and number of pods)
55
55
* calculates the currently required number of nodes per AWS Auto Scaling Group:
0 commit comments