-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Conversation
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.
👍
fargate/service-dedicated-alb.yaml
Outdated
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 |
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.
I would argue, that 60 seconds should be enough for most of the workloads? Speeds up the deployment process a lot.
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.
I agree
fargate/service-dedicated-alb.yaml
Outdated
Cluster: {'Fn::ImportValue': !Sub '${ParentClusterStack}-Cluster'} | ||
DeploymentConfiguration: | ||
MaximumPercent: 200 | ||
MinimumHealthyPercent: 50 |
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.
Why downgrading the capacity during a deployment? Especially, as we are using Fargate? I'd recommend 100%.
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.
good catch
[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
Support for AWS Fargate
Todos
NLB integrationChanges
fargate/cluster
- Fargate clusterfargate/service-dedicated-alb
- Fargate service that runs on a Fargate cluster based on fargate/cluster.yaml and uses a dedicated ALBecs/cluster
- Optional support for ALB access logging and idle timeoutecs/service-dedicated-alb
- Optional support for ALB access logging and idle timeoutecs/service-dedicated-alb
- Added parameters to controlCpu
,Memory
,AutoScaling
, andHealthCheckGracePeriod
ecs/service-cluster-alb
- Added parameters to controlCpu
,Memory
,AutoScaling
, andHealthCheckGracePeriod