Description
Regardless of the dry-run parameter value, the watcher can issue draining commands and autoscaling group size reduction:
sokar/scaler/watchScalingObject.go
Line 46 in f1f98ad
Reproduction:
- Run sokar with
SK_SCA_MODE:"nomad-dc"
andSK_DRY_RUN:"1"
- Modify autoscaling group to have desired size more than
SK_SCALE_OBJECT_MAX
- Observe autoscaling group modified by sokar after
SK_SCA_WATCHER_INTERVAL
time
Is it a desired behavior or is it better not to apply any changes to infrastructure if sokar is in dry-run?