Currently, the kbin.social instance has planned maintenance. They are busy upgrading the infrastructure to Kubernetes, using Docker containers. They said it shouldn’t take much longer than 1 hour downtime in total (if everything goes fine).
The migration will help to dynamically scale the instance, to remove the growing pains. And hopefully increase the availability (uptime) as well.
Soon additional setup configurations, best server practices and ansible playbooks will be shared with the community.
In the meanwhile you can of course use other instances (I bet you are reading this message right now from another instance).
Actually excited for this (currently rolling out a k3s environment at work). For instances like this, the in demand scaling will be clutch.
Helm chart when?