Investigate replacing AWS ECS with AWS EKS
freakboy3742 opened this issue · comments
BeeKeeper currently uses AWS Elastic Container Service (ECS) to deploy build jobs. However, this is an AWS-specific API.
Amazon just announced EKS - Elastic Kubernetes Service - which would still be an Amazon service, but would allow us to use Kubernetes APIs, rather than proprietary AWS ones.
This should ultimately allow end users to run their own build clusters on their own machines, or deploy to infrastructure other than AWS.
We need someone to investigate the feasibility of this, and if it's plausible, implement a port to EKS (ideally abstracting away any AWS-specific API calls)
I'm interested in working on this.
@bkarlovitz Then by all means - please have a shot! The internals of Beekeeper aren't all that well documented, but if you have any questions, or want to have a video chat to get you started, let me know!
@freakboy3742 I'll take a first look through everything and let you know here if I need anything to get going. Thanks!
Hello! I did some digging, and have posted my notes on the wiki here: https://github.com/pybee/beekeeper/wiki/Notes-on-Getting-Beekeeper-on-Kubernetes
I'm going to keep plugging away, but there's at least a start.
Also we probably want to explore https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/