Hi,
thanks a lot for the great documentation on how to setup a codabench instance. @pauloguilhermepp and I are trying to run Codabench on Kubernetes and we were wondering if you have any recommendations or experience with that? We have been working on a helm chart, that @pauloguilhermepp would be happy to contribute if there is any interest from your side.
Our approach at the moment is to replicate the environment from the docker compose that you provide to this helm chart and we were wondering how to approach the execution of user submissions. If we understand correctly, the compute worker interacts with the docker daemon on the host via the mounted socket. There could be ways of doing this in Kubernetes as well, e.g. via interacting with the Container Runtime Interfaces on the nodes but we were wondering if an approach using the Kubernetes API itself would be helpful. In this setting, the django component (or another component) would interact with the Kubernetes API server to run submission pods which Kubernetes would then schedule and orchestrate.
We are happy to hear your opinions on that!
Best,
Paulo and Hannes
Hi,
thanks a lot for the great documentation on how to setup a codabench instance. @pauloguilhermepp and I are trying to run Codabench on Kubernetes and we were wondering if you have any recommendations or experience with that? We have been working on a helm chart, that @pauloguilhermepp would be happy to contribute if there is any interest from your side.
Our approach at the moment is to replicate the environment from the docker compose that you provide to this helm chart and we were wondering how to approach the execution of user submissions. If we understand correctly, the compute worker interacts with the docker daemon on the host via the mounted socket. There could be ways of doing this in Kubernetes as well, e.g. via interacting with the Container Runtime Interfaces on the nodes but we were wondering if an approach using the Kubernetes API itself would be helpful. In this setting, the django component (or another component) would interact with the Kubernetes API server to run submission pods which Kubernetes would then schedule and orchestrate.
We are happy to hear your opinions on that!
Best,
Paulo and Hannes