- Summary: “mybinder.org” is a public service managed by the JupyterHub team. It faced challenges due to lack of cloud credits and lost capacity. The 2i2c team joined the federation with a single-node BinderHub instance at “2i2c.mybinder.org” to provide a cheaper and simpler solution. Cloud infrastructure has become cheaper and commodified with matured Kubernetes and open source object storage options. Deploying BinderHub on a single-node VM is cheaper and reduces complexity. “2i2c.mybinder.org” now serves 70% of the federation and others can join using this approach. There is a need for more resources to sustain the node and cover development time.
Main points:
- “mybinder.org” had capacity issues with Google and lost more capacity, leaving only GESIS and OVH as federation members.
- 2i2c deployed a single-node Kubernetes instance on Hetzner cloud using K3s, which is cheaper and easier to manage.
- Managed Kubernetes services are complex and expensive, while single-node VMs offer a cheaper alternative.
- “2i2c.mybinder.org” now serves 70% of the federation and is being monitored for performance.
- Others can join the federation using the single-node BinderHub workflow with a guide provided.
- There is a need for more resources to sustain the node and cover development time.
Key details:
- Kubernetes has matured and there are more ways to run it, like single-node workflows with K3s.
- Managed object storage services have more open source options and are cheaper.
- Hetzner offers single-node VMs that are 4x cheaper than others and provides managed object storage.
- A single VM with K3s can handle around 400 simultaneous sessions at a lower cost than a scalable Kubernetes cluster.
- 2i2c is sponsoring the node with €350 a month and providing in-kind labor.
- A guide for deploying a BinderHub with K3s is available.
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。