Support for Kubernetes-like setups where you have possibly multiple containers for the backend and frontend that operate on the same database and don't have any state on their own (and can be spun up and shut down on demand).
The frontend doesn't have a state at all which means there is no reason this shouldn't work for the frontend already. For the runners high availability is also already possible because one can just create many runners (even running on the same machine). Each runner requires their own runner token but otherwise doesn't have a permanent state.
The backend however would require support for its database solution for this. This would probably entail switching from sqlite to mysql or postgresql.
Support for Kubernetes-like setups where you have possibly multiple containers for the backend and frontend that operate on the same database and don't have any state on their own (and can be spun up and shut down on demand).
The frontend doesn't have a state at all which means there is no reason this shouldn't work for the frontend already. For the runners high availability is also already possible because one can just create many runners (even running on the same machine). Each runner requires their own runner token but otherwise doesn't have a permanent state.
The backend however would require support for its database solution for this. This would probably entail switching from sqlite to mysql or postgresql.