The mybinder.org Site Reliability Engineering (SRE) team is an open group of community members that operate mybinder.org. They keep mybinder.org running smoothly and up-to-date. If you’re interested in learning more about operating mybinder.org, or would like to join the team have a look at the mybinder.org SRE documentation and a post in this forum called “The Operators”.
We generally keep deployment-related chatter to the mybinder.org-deploy gitter channel. However, we recognize that many folks aren’t on Gitter which is why we will use this thread to post occasional updates on the status of mybinder.org and planned outages or upgrades.
Incident: node pool outage during an upgrade
Recently @betatim upgraded Kubernetes on the mybinder.org deployment. This surfaced a bug whereby the ingress pod was on a cordoned node and thus wasn’t able to accept traffic. Details here: https://mybinder-sre.readthedocs.io/en/latest/incident-reports/2019-04-03-ingress-cordoned.html
mybinder.org is now running the latest BinderHub and repo2docker.
mybinder.org is now running the latest repo2docker.
Many thanks to @sgibson91 for the deploy
mybinder.org is now running the latest BinderHub and repo2docker .
The update to repo2docker should fix a problem with websockets not working properly that was reported in (amongst other places) Debugging your Binder
mybinder.org is now running the latest BinderHub
mybinder.org just got a new version of repo2docker. This brings the newest version of nteract_on_jupyter, the latest
notebook version (5.7.8) and pip v19.
mybinder.org just got a new version of BinderHub!
Many thanks to @brylie!
mybinder.org just received an update that makes it better at spreading repository builds across the cluster. This should keep the load on individual nodes lower instead of all repository builds clumping together on a single node.
mybinder.org has been updated with a new version of repo2docker.
- We now get conda 4.6 for builds which hopefully will speed up things a bit.
- We moved the notebook server and packages a user asks to have installed into their own conda environment (instead of using the root environment). This should be transparent to users, unless you were doing weird things and relying on the name of the environment or something.
mybinder.org is now running the latest repo2docker
mybinder.org is now running the latest repo2docker, should be caught up to release .9