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

Create a support cluster with debugging & deployment tooling #438

Closed
yuvipanda opened this issue Feb 21, 2018 · 4 comments
Closed

Create a support cluster with debugging & deployment tooling #438

yuvipanda opened this issue Feb 21, 2018 · 4 comments

Comments

@yuvipanda
Copy link
Contributor

Currently, tools critical to deploying changes are running in the same cluster they are deploying to. This includes at least Grafana, and possibly new tools being added (#425, etc).

These should be in a separate cluster that is in a different region than the one we run, to make sure they can stay up regardless of various problems we might be having.

@minrk
Copy link
Member

minrk commented Feb 21, 2018

Makes sense. Re: file layout, does this mean putting a mybinder-support directory with grafana, etc. next to mybinder with the Binder deployment itself?

@yuvipanda
Copy link
Contributor Author

There are two options:

  1. Have a top-level 'mybinder-support' or 'support' dir in this repo
  2. Make a different repo that has just these.

I'm torn between preferring (1) for simplicity but (2) for full isolation, since it'll let us deploy to support code even in times when our primary deployment is fubar.

@choldgraf
Copy link
Member

I'm happy with either of these options

@yuvipanda
Copy link
Contributor Author

I think we decided to not have a separate cluster just for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants