Releases: freepik-company/custom-vm-autoscaler
Releases · freepik-company/custom-vm-autoscaler
v1.2.6
Fixes
- Add un-drain of the node if timeout is reached draining it
Contributors
v1.2.5
v1.2.4
v1.2.3
Notes
- Fixed Slack error messages when no further scaling up or down is possible due to reaching limits
Contributors
v1.2.1
Notes
- Added support for many autoscalers checking previously configuration in Elasticsearch cluster settings and not removing it.
- Increased verbosity with more slack error messages.
- Added debugMode more deeper for debugging better :D .
- Timeout draining node from elasticsearch, avoiding infinity loops.
- Support for no elasticsearch configuration and just scaling
Contributors
v1.2.0
Notes
- Renamed to cluster-vm-autoscaler
- Refactor of code using Cobra
- Refactor of configuration adding a config file
Contributors
v1.1.1
Notes
- Fixed security issues with the application
-
- Unhandled Errors
-
- Wark Math Random Algorithm
-
- Writable Filesystem service in prometheus example
-
- Missing SSL minVersion
Contributors
v1.1.0
Notes
- Changed ownership to freepik-company
v1.0.4
Notes
- Added suport for 3 new environment variables to allow critical periods where the minimum size of nodes must be higher
-
- CRITICAL_PERIOD_HOURS_UTC: Critical hours where MIG needs at least a minimum nodes to work properly (
Optional
) (Example: "6:00:00-8:00:00")
- CRITICAL_PERIOD_HOURS_UTC: Critical hours where MIG needs at least a minimum nodes to work properly (
-
- CRITICAL_PERIOD_DAYS: Critical days where MIG needs at least a minimum nodes to work properly (
Optional
) (Example: "2,3,4")
- CRITICAL_PERIOD_DAYS: Critical days where MIG needs at least a minimum nodes to work properly (
-
- MIN_NODES_CRITICAL_PERIOD: Minimum nodes for critical period to exist (
Optional
)
- MIN_NODES_CRITICAL_PERIOD: Minimum nodes for critical period to exist (