Memory metric in now optional in autoscaler module. However, a bunch of default values is still available to be used.
Motivation and context
NodeJS keeps to fill half of the available memory, making the setup of a generic scale-in rule difficult. I remind that an and operator is used among scale-in rules. Then, Memory should be optional to accomodate the highest number of cases.
Users already using memory metric, or are interested in it, should set memory = {}. This gets default values provided by the module. However, each value is overridable.
Type of changes
[ ] Add new resources
[X] Update configuration to existing resources
[ ] Remove existing resources
Does this introduce a change to production resources with possible user impact?
[X] Yes, users may be impacted applying this change
List of changes
Memory metric in now optional in autoscaler module. However, a bunch of default values is still available to be used.
Motivation and context
NodeJS keeps to fill half of the available memory, making the setup of a generic scale-in rule difficult. I remind that an
andoperator is used among scale-in rules. Then,Memoryshould be optional to accomodate the highest number of cases.Users already using
memorymetric, or are interested in it, should setmemory = {}. This gets default values provided by the module. However, each value is overridable.Type of changes
Does this introduce a change to production resources with possible user impact?
Other information