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.

Sign up for GitHub

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

Jump to bottom

automate setup/teardown for testing cluster #15

Open
3 of 4 tasks
slugalisk opened this issue Jun 2, 2020 · 3 comments
Open
3 of 4 tasks

automate setup/teardown for testing cluster #15

slugalisk opened this issue Jun 2, 2020 · 3 comments
Assignees
@x-Xymos
Labels
enhancement New feature or request ops Infrastructure automation

Comments

@slugalisk
Copy link
Member

slugalisk commented Jun 2, 2020 •
edited
Loading

To automate e2e testing we want to be able to spin up a multi-region kubernetes cluster in digitalocean. DO bandwidth pricing makes it a nonstarter for production deployment so while they do offer a hosted k8s solution it may make sense to roll our own especially if this comes with significant vendor lockin. We should investigate and decide whether the tradeoff for reusability vs ease of use makes sense...

  • investigate do hosted solution

cluster services:

  • prometheus
  • grafana
  • cmd/svc
@slugalisk slugalisk added enhancement New feature or request question Further information is requested ops Infrastructure automation labels Jun 2, 2020
@x-Xymos
Copy link
Collaborator

x-Xymos commented Jun 5, 2020 •
edited
Loading

I dunno about digital ocean but spinning up your own kubernetes cluster on a node/VM takes seconds, then all you gotta do is spin up some slave nodes and join the cluster. I imagine a self managed solution will be a lot cheaper

@slugalisk slugalisk removed the question Further information is requested label Jun 7, 2020
@slugalisk
Copy link
Member Author

@x-Xymos perfect, can we work on this next?

@jbpratt
Copy link
Member

jbpratt commented Jul 25, 2020 •
edited
Loading

containerd/containerd#3291
Blocking pulling directly from GitHub's registry, we are trying to work around this currently pushed to a private DockerHub repo for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@x-Xymos x-Xymos

Labels
enhancement New feature or request ops Infrastructure automation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@slugalisk @jbpratt @x-Xymos