[Terraform] EKS Fargate #100
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies our EKS cluster to use Fargate as a backend rather than EC2 instances. This allows us to not worry about the underlying EC2 VMs and instead just schedule pods into the ether.
TODO:
There is a problem where Fargate uses resource requests to determine the amount of CPU and RAM to give to the container. Icarus doesn't define these, so AWS defaults to the smallest value which is not enough for the penn courses backend. This results in the pod being killed over and over for Out Of Memory problems. Once we migrate to Kittyhawk, we can provide defaults for django, react, and general defaults to solve this problem.