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

Proposal: Remove support for unused/under-tested stacks #107

Open
tobiasmcnulty opened this issue Feb 14, 2021 · 0 comments
Open

Proposal: Remove support for unused/under-tested stacks #107

tobiasmcnulty opened this issue Feb 14, 2021 · 0 comments

Comments

@tobiasmcnulty
Copy link
Member

To help reduce the maintenance burden of maintaining many stacks, I'd like to remove some of the stacks we don't use at Caktus any more.

If anyone in the community uses any of these and would like to help maintain them, please speak up!

The candidates for removal that initially come to mind are:

  • Elastic Container Service (ECS): ECS has never felt like a good fit for any project that I can remember.
  • Dokku: These days, it's probably better to use the EC2 stack and install Dokku manually or via Ansible oneself.

I'm on the fence about:

  • Elastic Beanstalk (EB): It's nice to have a stack that supports containers but that doesn't involve the overhead of Kubernetes, but the second you need to run Celery or any other job, you're out of luck.

This would involve keeping (at least):

  • Elastic Kubernetes Service (EKS)
  • Elastic Compute Cloud (EC2)

I could imagine adding support for the recently-introduced container runtime for Lambda (https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/) at some point, which might provide a nice replacement for ECS, EB, and potentially Dokku as well.

What do others think? Would you like to see any of the proposed candidates for removal stay around, and how are they being used, if so?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant