-
Notifications
You must be signed in to change notification settings - Fork 67
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
Automated cluster setup for AWS #627
Comments
I am a bit confused about the state of our AWS cluster setup. In this description it says:
but our pilot hubs documentation is all about Either way, I've opened up #737 and added it above as a step towards completing this |
Just to clarify... We use kops for Openscapes and Farallon clusters AND we use EKS (and eksctl) for the Carbonplan cluster. On a brief comment in 737, I have said why I believe we should keep both for a little bit until we collect enough information to decide and resolve #431. |
This is done now - we have https://github.com/2i2c-org/infrastructure/blob/master/docs/howto/operate/new-cluster/aws.md. eksctl creates the cluster, and we have terraform for all other work. I'd say we can close this for now. The next step would be to remove eksctl completely, but I think that requires aws/containers-roadmap#724 to be solved. |
Description
We use
eksctl
for setting up AWS clusters. The setup isn't fully automated yet, however. We should use a combination of documentation + any required helper scripts to automate the entire setup.Benefit
Automating our AWS clusters will allow us to standardize and automate our infrastructure, which is an important part of scaling our infrastructure and ensuring that it behaves consistently across all of our clusters.
Tasks to complete
eksctl
#737Port over this code for authentication:https://github.com/yuvipanda/hubploy/blob/dfc00254abb30d8887230472e83b405ff5872933/hubploy/auth.py#L107The text was updated successfully, but these errors were encountered: