Skip to content

Releases: freepik-company/custom-vm-autoscaler

v1.2.6

19 Dec 09:29
Compare
Choose a tag to compare

Fixes

  • Add un-drain of the node if timeout is reached draining it

Contributors

@jmjimenezlp @dfradehubs

v1.2.5

25 Nov 10:54
2f6049e
Compare
Choose a tag to compare

Notes

  • Added new feature for scaling up nodes more than one by one

Contributors

@dfradehubs

v1.2.4

06 Nov 13:34
Compare
Choose a tag to compare

Notes

  • Fixed bug when no settings was in exclude directive

Contributors

@dfradehubs

v1.2.3

06 Nov 08:11
Compare
Choose a tag to compare

Notes

  • Fixed Slack error messages when no further scaling up or down is possible due to reaching limits

Contributors

@dfradehubs

v1.2.1

06 Nov 07:27
3c46e07
Compare
Choose a tag to compare

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

@dfradehubs

v1.2.0

30 Sep 11:44
3f93662
Compare
Choose a tag to compare

Notes

  • Renamed to cluster-vm-autoscaler
  • Refactor of code using Cobra
  • Refactor of configuration adding a config file

Contributors

@dfradehubs

v1.1.1

27 Sep 07:10
Compare
Choose a tag to compare

Notes

  • Fixed security issues with the application
    • Unhandled Errors
    • Wark Math Random Algorithm
    • Writable Filesystem service in prometheus example
    • Missing SSL minVersion

Contributors

@dfradehubs

v1.1.0

25 Sep 13:31
Compare
Choose a tag to compare

Notes

  • Changed ownership to freepik-company

v1.0.4

24 Sep 09:39
81a2ceb
Compare
Choose a tag to compare

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_DAYS: Critical days where MIG needs at least a minimum nodes to work properly (Optional) (Example: "2,3,4")
    • MIN_NODES_CRITICAL_PERIOD: Minimum nodes for critical period to exist (Optional)

Contributors

@dfradehubs

Reviewers

@rafalitox2

v1.0.3

20 Sep 08:04
0e78428
Compare
Choose a tag to compare

Notes

  • Create a new variable and set a default one on cooldown periods

Contributors

@rafalitox2