You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created a branch feat/eks where I've started to remove the current EC2 instance that runs the Container Service and replace it with EKS. It's using the terraform-aws-eks module to create a cluster with a managed node group.
However, I've just realised that this approach (with managed nodes) means the worker nodes are always running, even when no containers are running. So this wouldn't help reduce the cost of running the workshop. Instead we should try using Fargate.
There are some tutorials on setting up EKS with terraform-aws-eks:
There are some docs on using Kubernetes with the Container Service, and some scripts to create a kube config that is compatible with the Container Service (the kube config generated by aws eks update-kubeconfig cannot be used with the Container Service)
The text was updated successfully, but these errors were encountered:
To reduce the cost of running the workshop we could use the Elastic Kubernetes Service to deploy containers with Fargate
I've created a branch feat/eks where I've started to remove the current EC2 instance that runs the Container Service and replace it with EKS. It's using the
terraform-aws-eks
module to create a cluster with a managed node group.However, I've just realised that this approach (with managed nodes) means the worker nodes are always running, even when no containers are running. So this wouldn't help reduce the cost of running the workshop. Instead we should try using Fargate.
There are some tutorials on setting up EKS with
terraform-aws-eks
:There are some docs on using Kubernetes with the Container Service, and some scripts to create a kube config that is compatible with the Container Service (the kube config generated by
aws eks update-kubeconfig
cannot be used with the Container Service)The text was updated successfully, but these errors were encountered: