-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
horizontal pod scaling, v1 #154
Conversation
…olicy as a starting point
…etrics optionally
Plan for stagingTerraform Format and Style 🖌
|
Plan for devTerraform Format and Style 🖌
|
Plan for prodTerraform Format and Style 🖌
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you!
Oof the dynamic ignore changes in modules seems like a long-standing feature request hashicorp/terraform#24188 |
Yeah, all of my digging has turned up that we're basically stuck putting ignore_changes on in the module. I think that's probably fine. Can we maybe bump the default desiredcount to 2 (probably best to see if there is any weird 2 instance behavior in dev anyway) and then add ignore_changes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small things/qs, but ready when you are
Plan for devTerraform Format and Style 🖌
|
Plan for stagingTerraform Format and Style 🖌
|
Plan for prodTerraform Format and Style 🖌
|
This PR adds a module + an initial configuration for staging's deployment to do horizontal pod scaling via a "target tracking" policy type.
E.g. this adjusts the ECS
DesiredCount
setting for the service to crank the number of worker containers based on a autoscaling-controlled metric.AWS docs advise against touching the service-created metric (if we want direct control over the metric we need to use a different policy type).
The ECS cluster has a capacity provider that will scale up more instances to accommodate demand.
TODO:
DesireCount
on the app to be ignored via:Though, I am not clear on how to do this in a multi-module world.