Change Details

I'm filing this as a placeholder followup from T292094, where I mentioned: > After discussion today with SRE folks, we also expect to build: > … > * Untrusted and variously constrained runners, probably on a 3rd-party host, to handle user-level projects and merge requests from forks. > * This will be experimental, and a bunch of details will need to be worked out. Further detail to come.

I'm filing this as a placeholder followup from T292094, where I mentioned: > After discussion today with SRE folks, we also expect to build: > … > * Untrusted and variously constrained runners, probably on a 3rd-party host, to handle user-level projects and merge requests from forks. > * This will be experimental, and a bunch of details will need to be worked out. Open problems: [x] provision managed Kubernetes cluster on Digital Ocean [x] configure Kubernetes executor using `gitlab/gitlab-runner` helm chart [x] create ci-pipeline for both above ([repos/releng/gitlab-cloud-runner/](https://gitlab.wikimedia.org/repos/releng/gitlab-cloud-runner/)) [x] reduce timeout for CI jobs to 10m for Cloud Runners [x] reduce amount of CPU/MEM available to CI jobs [x] activate autoscaling for Kubernetes Node pool [] ~~create quota for available CI minutes~~ not possible in [free tier](https://docs.gitlab.com/ee/ci/pipelines/cicd_minutes.html). [] ...? [] create some kind of alerting or monitoring [] restrict allowed images? [] open Cloud Runners instance wide [] announce Cloud Runners?

I'm filing this as a placeholder followup from T292094, where I mentioned: > After discussion today with SRE folks, we also expect to build: > … > * Untrusted and variously constrained runners, probably on a 3rd-party host, to handle user-level projects and merge requests from forks. > * This will be experimental, and a bunch of details will need to be worked out. Further detail to come.Open problems: [x] provision managed Kubernetes cluster on Digital Ocean [x] configure Kubernetes executor using `gitlab/gitlab-runner` helm chart [x] create ci-pipeline for both above ([repos/releng/gitlab-cloud-runner/](https://gitlab.wikimedia.org/repos/releng/gitlab-cloud-runner/)) [x] reduce timeout for CI jobs to 10m for Cloud Runners [x] reduce amount of CPU/MEM available to CI jobs [x] activate autoscaling for Kubernetes Node pool [] ~~create quota for available CI minutes~~ not possible in [free tier](https://docs.gitlab.com/ee/ci/pipelines/cicd_minutes.html). [] ...? [] create some kind of alerting or monitoring [] restrict allowed images? [] open Cloud Runners instance wide [] announce Cloud Runners?