-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: K8S IaC - GitOps with ArgoCD #2
Conversation
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
Signed-off-by: Smuu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic job!
repo_url = "https://github.com/celestiaorg/testground-infra.git" | ||
target_revision = "jose/hackground-k8s-tf" // Remove this one, should use main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need to prepare this to use testground/testground after this PR get's merged in out celestiaorg/testground and we do a proper PR to upstream
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly, I had the same idea, after we merge this PR, we'll be able to test it using the celestia repo, if everything works (it should), then, I'll prepare a new PR pointing to the final repo: testground/infra
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic job!
Discard my approve :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge this and do a PR in testground/infra
Description 📜
Hello team!
First of all, let me apologize for the size of this PR 🙏
TLDR:
This PR contains a lot of changes in the way that we create and provision the Kubernetes clusters for TestGround.
Original approach: ⛳️
We started developing the IaC with Terraform (EKS) + ArgoCD, but after some tests, we realized that EKS has some limitations when we need to run big clusters (>7k tests pods), this is because the CP ( K8S ControlPlane) is self-managed by AWS, and the amount of resources is managed by them.
Then, we pivoted to: 🎯
After a while, we decided to move to Kops, and following the same approach, IaC + GitOps, we now have the cluster creation with Kops + ArgoCD.
Some benefits of using this approach:
ℹ️ Also, mention that both clusters are functional, you can use either of them (EKS/Kops).
Thanks in advance!
What's included in this PR 🧐
v1.23.4
-> latest K8S version we can use while running Docker as CRI.ℹ️ Once we merge this PR, we will have to update all the references to this branch.
Closes: celestiaorg/devops#123
Best 🚀
Jose Ramon Mañes