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(env): associate FARGATE and FARGATE_SPOT cap providers with cluster #1044

Merged
merged 2 commits into from
Jun 22, 2020
Merged

feat(env): associate FARGATE and FARGATE_SPOT cap providers with cluster #1044

merged 2 commits into from
Jun 22, 2020

Conversation

efekarakus
Copy link
Contributor

The FARGATE and FARGATE_SPOT capacity providers are already
created and available to all accounts in Regions supported by AWS
Fargate. With this change we associate these cap providers with the
cluster, this way we can start running tasks on FARGATE_SPOT.

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

The FARGATE and FARGATE_SPOT capacity providers are already
created and available to all accounts in Regions supported by AWS
Fargate. With this change we associate these cap providers with the
cluster, this way we can start running tasks on FARGATE_SPOT.
@efekarakus efekarakus requested review from kohidave and a team June 22, 2020 18:30
@efekarakus
Copy link
Contributor Author

Here is a new env that I created that gets associated with FARGATE and FARGATE_SPOT
Screen Shot 2020-06-22 at 11 30 56 AM

Copy link
Contributor

@bvtujo bvtujo left a comment

Choose a reason for hiding this comment

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

Awesome!

Copy link
Contributor

@iamhopaul123 iamhopaul123 left a comment

Choose a reason for hiding this comment

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

👍

@mergify mergify bot merged commit 0c20b23 into aws:master Jun 22, 2020
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