Clone ECS Service into another Cluster about containers-roadmap HOT 9 OPEN

Please show some manners and support the idea by thumbs-up on the original post, rather than wasting people’s time and inboxes with +1 posts.

@pilgrim2go if your services are compatible with EKS then it supports multiple node groups per cluster, so you can have both a fixed and autoscale node groups in a cluster, then run services on the cluster and utilize both node pools.

from containers-roadmap.

Hi @pilgrim2go. Thanks for the suggestion. I wonder how much of this belongs in the ECS service itself and how much may be more appropriate for the ECS CLI or other developer tooling. What would you envision as a preferred workflow for cloning services between clusters?

from containers-roadmap.

@nmeyerhans : I'm not pretty sure.
Task Definition is a standalone object. I can be run into any cluster.
Service could be a standalone object and then we can run it into any cluster also. Why not?
I'm asking this since creating service in UI is not simple as was before. Now we have to configure ALB/Target Group and Auto Scaling.
So a simple clone in service and simply selecting new cluster is much more easier for me and less error prone.

from containers-roadmap.

+1

from containers-roadmap.

+1

from containers-roadmap.

+1

from containers-roadmap.

+1

from containers-roadmap.

This would be great!

from containers-roadmap.

Hello, I have the same use case (two cluster on demand/spot with autoscaling).
We simply declare a service on each with specific autoscaling configuration (all this stuff is scripted).
AMHO, I think if you just 'clone' ie: change cluster target of your service, it's not enough. You have to deal with specific deployment constraint also.

from containers-roadmap.