-
Notifications
You must be signed in to change notification settings - Fork 66
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
Convert AWS cluster deployment workflow to eksctl
#737
Comments
👍
I think we are still in the "getting info" phase, I would wait a little bit more... |
@yuvipanda, do you have any notes from the |
eksctl
eksctl
This is done! https://github.com/2i2c-org/infrastructure/blob/master/docs/howto/operate/new-cluster/aws.md. However, I think farallon still needs to be moved. |
I've created #737 to track kops migration of farallon, but we can close this now. |
Description
Our current process for deploying AWS clusters is to use
kops
(e.g., docs on how to deploy an AWS cluster withkops
). However, in #431 (comment) we've provided a rationale for moving fromkops
toeksctl
. This issue will track that migration.Value / benefit
See #431 (comment) for the rationale about "why
eksctl
" but more generally if we standardize on a single system for deploying clusters on AWS, it will help us reduce complexity and standardize our team practices, which will reduce uncertainty and information silos.Tasks to complete
EKS
eksctl
: Automate and document setting up eksctl clusters #885kops
to instead useeksctl
eksctl
#737(probably needs to be done by either @yuvipanda or @damianavila)
Updates
eksctl
The text was updated successfully, but these errors were encountered: