4 ms·
> here's the proprietary part: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/.. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/....
by bdcravens 7y ago
> here's the proprietary part: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/.. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/....
That's ECS, not EKS. Two different products.
The EKS documentation is at https://docs.aws.amazon.com/eks/latest/userguide/fargate.html https://docs.aws.amazon.com/eks/latest/userguide/fargate.htm...
> For contrast, you can manage a Kubernetes deployment using standardized yaml and kubectl commands, regardless of whether the application is running on localhost (minikube), on Azure or on GKE.
Likewise for EKS.
- petilon 7y agoI was replying to this: > At the low end it’s worth considering Fargate distinct from EKS.
- txcwpalpha 7y agoRight, and you linked to the documentation for ECS on Fargate rather than the documentation for Kubernetes Fargate, which is what was being talked about. Again, two different products.