4 ms·
AWS employee here. You would deploy to Fargate because you don't want to have to manage the underlying EC2 instances. You can use Fargate with both ECS and EKS
by NathanKP 9y ago
AWS employee here. You would deploy to Fargate because you don't want to have to manage the underlying EC2 instances. You can use Fargate with both ECS and EKS (in 2018).
ECS and EKS are just two different schedulers for orchestrating the containerized services that you want to run. Fargate is the engine behind them that executes the containers for you without you needing to worry about servers.
ECS as a scheduler will always integrate much better with other AWS services. EKS will give you the advantage of being able to run the same scheduler on an on premise or on another cloud.
- mgalgs 9y agoI thought EKS was managed? Do you still have to manage the underlying instances in EKS?
- kainosnoema 9y agoYes, EKS is just managed K8s, which is the orchestration layer. You still need to have EC2 instances for the EKS tasks to be scheduled on. Unless you run your EKS tasks on Fargate, which is coming in 2018.
- avgkol 9y agoSo if I do "kubectl get nodes" while using Fargate, what do I see in response?
- chkal 9y agoThanks a lot for the explanation.