You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Makes sense. Re: file layout, does this mean putting a mybinder-support directory with grafana, etc. next to mybinder with the Binder deployment itself?
Have a top-level 'mybinder-support' or 'support' dir in this repo
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.
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.
The text was updated successfully, but these errors were encountered: