Open minrk opened 2 years ago
I like the idea of a clean separation in projects between the gke.mybinder.org
binderhub, and the "core federation router" infrastructure. +1 on this proposal from me.
Sounds good to me, and will also help with local testing and development of just the core infra/redirector.
The pressure is off a bit on the GKE funding (thanks @choldgraf!), but to alleviate issues in the future, I think we should split the 'hard to turn off' features running on GCP (federation-redirect, matomo, events archive, central grafana) from the GKE "user" (and staging?) clusters, which drive most of the cost, and are more easily turned off when we have a healthy federation.
This will make it easier to turn the GKE cluster all the way off, while leaving us with a small, manageable bill for 'core' functionality, backed by donations, stop-gap funding, etc. Cost estimates suggest this should be in the much more manageable range of hundreds of dollars/month, not thousands.
For migration purposes, I think it's best to leave the current
binderhub
project as the long-term one (avoids annoying matomo, events-archive, mybinder.org DNS migration), and start a new project for the federation member. With the intention that the current project never stops running and has sustainable funding via donations, etc.Steps:
mybinder-gke
)Note: because this involves an additional cluster, our overall GKE bill will likely go up as a result. But it shouldn't be a lot, because the new 'core' cluster will have minimal requirements. But the new prod cluster will likely not have appreciably reduced requirements (prometheus, jupyterhub, binderhub are ~everything).
Two smaller alternatives:
These are slightly simpler from a management perspective. The only real downsides to this that I can see are: