-
-
Notifications
You must be signed in to change notification settings - Fork 12
Rework Kubernetes deployment to use EKS+fargate for everything #143
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
Conversation
Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
…ternal-dns debug logging Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
… they recognize the new names Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
…mall managed node Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
i am out of my depth on this one, @irvingpop - sorry! |
one thought, regarding the infrastructure node. Because of CNI limitations a a |
Signed-off-by: Irving Popovetsky <irving@honeycomb.io>
Update: So that the kops cluster isn't impacted, I've created a |
It's a difference of like $2 a month. I say just go for it. |
Problem: Our current Kubernetes cluster is too expensive to run and also has manageability challenges.
This PR's goal is to fully document the new
operationcode-backend
EKS cluster, so that it can be rebuilt if there's ever a need. Nearly everything runs "serverless" via Fargate, which should save a considerable amount of money. The only exception is ArgoCD, which requires persistent volumes, must run on an EC2 node.Add configs for:
Remove:
Rework:
Fixes: #138
Fixes: #139
Signed-off-by: Irving Popovetsky irving@honeycomb.io