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

Automated cluster setup for AWS #627

Closed
3 tasks done
yuvipanda opened this issue Aug 23, 2021 · 3 comments
Closed
3 tasks done

Automated cluster setup for AWS #627

yuvipanda opened this issue Aug 23, 2021 · 3 comments
Labels
Enhancement An improvement to something or creating something new.

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Aug 23, 2021

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

Port over this code for authentication:
https://github.com/yuvipanda/hubploy/blob/dfc00254abb30d8887230472e83b405ff5872933/hubploy/auth.py#L107

@yuvipanda yuvipanda added the Task Actions that don't involve changing our code or docs. label Aug 23, 2021
@choldgraf choldgraf added 🏷️ CI/CD Enhancement An improvement to something or creating something new. and removed Task Actions that don't involve changing our code or docs. labels Aug 26, 2021
@choldgraf
Copy link
Member

choldgraf commented Oct 5, 2021

I am a bit confused about the state of our AWS cluster setup. In this description it says:

We use eksctl for setting up AWS clusters

but our pilot hubs documentation is all about kops rather than eksctl (https://devops.2i2c.org/en/latest/howto/operate/new-cluster/aws.html). Is the plan to move away from kops in general, in favor of eksctl? (I am definitely in favor of only using 1 pathway instead of 2)

Either way, I've opened up #737 and added it above as a step towards completing this

@damianavila
Copy link
Contributor

Just to clarify...

We use kops for Openscapes and Farallon clusters AND we use EKS (and eksctl) for the Carbonplan cluster.
There is an ongoing ticket to compare both at #431.

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.

@choldgraf choldgraf changed the title Automate cluster setup for AWS [Project] Automate cluster setup for AWS Dec 7, 2021
@choldgraf choldgraf changed the title [Project] Automate cluster setup for AWS Automate cluster setup for AWS Dec 7, 2021
@choldgraf choldgraf changed the title Automate cluster setup for AWS Automated cluster setup for AWS Dec 7, 2021
@choldgraf choldgraf moved this to Needs Shaping / Refinement in DEPRECATED Engineering and Product Backlog Dec 8, 2021
@yuvipanda
Copy link
Member Author

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.

Repository owner moved this from Needs Shaping / Refinement to Complete in DEPRECATED Engineering and Product Backlog Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new.
Projects
No open projects
Development

No branches or pull requests

3 participants