Skip to content
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

Use EKS and Fargate for the Container Service #76

Open
p-j-smith opened this issue Aug 21, 2023 · 3 comments
Open

Use EKS and Fargate for the Container Service #76

p-j-smith opened this issue Aug 21, 2023 · 3 comments
Labels
enhancement New feature or request priority-medium

Comments

@p-j-smith
Copy link
Contributor

p-j-smith commented Aug 21, 2023

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)

@p-j-smith
Copy link
Contributor Author

@p-j-smith
Copy link
Contributor Author

There are lots of tutorials here for terraform / kubernetes / aws:

@milanmlft
Copy link
Collaborator

WIP on the feat/eks branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-medium
Projects
None yet
Development

No branches or pull requests

3 participants