Skip to content
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

feat(templates): enable autoscaling for simple target track policies #1355

Merged
merged 2 commits into from
Sep 4, 2020

Conversation

iamhopaul123
Copy link
Contributor

Part of #1349. Enable Auto Scaling for simple target track policies by updating CFN template. Will add e2e test in a separate PR after this one. Also will add a custom resource to set desiredCount smartly so that when users update their ECS service there won't be a sudden increment/decrement to their task num.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@iamhopaul123 iamhopaul123 requested a review from a team as a code owner September 3, 2020 21:58
@iamhopaul123
Copy link
Contributor Author

iamhopaul123 commented Sep 3, 2020

Manual Test

Below shows a manifest example that enables Auto Scaling and apply multiple target tracking policies to the auto scaling.

count:
  range: 1-10
  cpu_percentage: 70
  memory_percentage: 80

And after doing copilot svc deploy to deploy the service, we can see the auto scaling successfully applied to the ECS service.

Screen Shot 2020-09-03 at 3 01 11 PM

@iamhopaul123 iamhopaul123 changed the title feat(templates): enable autoscaling for simple target track policies feat(templates)!: enable autoscaling for simple target track policies Sep 3, 2020
@iamhopaul123 iamhopaul123 added the type/breaking-change Issues that introduce a backwards incompatible change label Sep 3, 2020
@iamhopaul123 iamhopaul123 changed the title feat(templates)!: enable autoscaling for simple target track policies feat(templates): enable autoscaling for simple target track policies Sep 3, 2020
@iamhopaul123 iamhopaul123 removed the type/breaking-change Issues that introduce a backwards incompatible change label Sep 3, 2020
Copy link
Contributor

@efekarakus efekarakus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@mergify mergify bot merged commit 3ce45ff into aws:mainline Sep 4, 2020
mergify bot pushed a commit that referenced this pull request Sep 16, 2020
<!-- Provide summary of changes -->
Since we now enable auto scaling in #1355. This feature enable `svc status` to show any alarms created by auto scaling. After this PR `svc status` should be able to show alarms created by auto scaling or alarms with copilot tags.
<!-- Issue number, if available. E.g. "Fixes #31", "Addresses #42, 77" -->

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
thrau pushed a commit to localstack/copilot-cli-local that referenced this pull request Dec 9, 2022
…ws#1355)

<!-- Provide summary of changes -->
Part of aws#1349. Enable Auto Scaling for simple target track policies by updating CFN template. Will add e2e test in a separate PR after this one. Also will add a custom resource to set `desiredCount` smartly so that when users update their ECS service there won't be a sudden increment/decrement to their task num.
<!-- Issue number, if available. E.g. "Fixes aws#31", "Addresses aws#42, 77" -->

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
thrau pushed a commit to localstack/copilot-cli-local that referenced this pull request Dec 9, 2022
<!-- Provide summary of changes -->
Since we now enable auto scaling in aws#1355. This feature enable `svc status` to show any alarms created by auto scaling. After this PR `svc status` should be able to show alarms created by auto scaling or alarms with copilot tags.
<!-- Issue number, if available. E.g. "Fixes aws#31", "Addresses aws#42, 77" -->

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants