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

Fargate support (3rd iteration) #249

Merged
merged 24 commits into from
Jan 8, 2019
Merged

Fargate support (3rd iteration) #249

merged 24 commits into from
Jan 8, 2019

Conversation

michaelwittig
Copy link
Contributor

@michaelwittig michaelwittig commented Jan 7, 2019

Support for AWS Fargate

Todos

Changes

  • [New Template] fargate/cluster - Fargate cluster
  • [New Template] fargate/service-dedicated-alb - Fargate service that runs on a Fargate cluster based on fargate/cluster.yaml and uses a dedicated ALB
  • [Improvement] ecs/cluster - Optional support for ALB access logging and idle timeout
  • [Improvement] ecs/service-dedicated-alb - Optional support for ALB access logging and idle timeout
  • [Improvement] ecs/service-dedicated-alb - Added parameters to control Cpu, Memory, AutoScaling, and HealthCheckGracePeriod
  • [Improvement] ecs/service-cluster-alb - Added parameters to control Cpu, Memory, AutoScaling, and HealthCheckGracePeriod

Copy link
Contributor

@andreaswittig andreaswittig left a comment

Choose a reason for hiding this comment

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

👍

LoadBalancerDeregistrationDelay:
Description: 'The amount time (in seconds) to wait before changing the state of a deregistering target from draining to unused.'
Type: Number
Default: 300
Copy link
Contributor

Choose a reason for hiding this comment

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

I would argue, that 60 seconds should be enough for most of the workloads? Speeds up the deployment process a lot.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree

Cluster: {'Fn::ImportValue': !Sub '${ParentClusterStack}-Cluster'}
DeploymentConfiguration:
MaximumPercent: 200
MinimumHealthyPercent: 50
Copy link
Contributor

Choose a reason for hiding this comment

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

Why downgrading the capacity during a deployment? Especially, as we are using Fargate? I'd recommend 100%.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good catch

@michaelwittig michaelwittig merged commit 935d24a into master Jan 8, 2019
@michaelwittig michaelwittig deleted the fargate3 branch January 8, 2019 07:54
andreaswittig pushed a commit that referenced this pull request May 16, 2019
[New Template] fargate/cluster - Fargate cluster
[New Template] fargate/service-dedicated-alb - Fargate service that runs on a Fargate cluster based on fargate/cluster.yaml and uses a dedicated ALB
[Improvement] ecs/cluster - Optional support for ALB access logging and idle timeout
[Improvement] ecs/service-dedicated-alb - Optional support for ALB access logging and idle timeout
[Improvement] ecs/service-dedicated-alb - Added parameters to control Cpu, Memory, AutoScaling, and HealthCheckGracePeriod
[Improvement] ecs/service-cluster-alb - Added parameters to control Cpu, Memory, AutoScaling, and HealthCheckGracePeriod
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants