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
Move comments to javadoc and give precedence to hard constraint checks (minimum instances, max instances) instead of aborting early due to tolerance area checks.
Copy file name to clipboardExpand all lines: src/main/java/cambio/simulator/entities/patterns/HorizontalPodAutoscalingPolicy.java
+19-17Lines changed: 19 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,21 @@
6
6
importcambio.simulator.parsing.JsonTypeName;
7
7
importdesmoj.core.simulator.TimeInstant;
8
8
9
+
/**
10
+
* AN implementation based on Kubernetes
11
+
* <a href="https://github.com/kubernetes/kubernetes/blob/8caeec429ee1d2a9df7b7a41b21c626346b456fb/docs/design/horizontal-pod-autoscaler.md#autoscaling-algorithm">Horizontal Pod Autoscaler</a>.
12
+
* <p>
13
+
* By default, scale-up can only happen if there was no rescaling within the last 3 minutes. Scale-down will wait for 5
14
+
* minutes from the last rescaling. Moreover, any scaling will only be made if: avg(CurrentPodsConsumption) / Target
15
+
* drops below 0.9 or increases above 1.1 (10% tolerance)
16
+
* <p>
17
+
* TODO Maybe also include via adapter, upscaling/downscaling behavior not 100% as in Kubernetes, e.g. see
0 commit comments