How do we configure GitLab CI runners to automatically scale down to zero when our remote team is not actively pushing code?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do we configure GitLab CI runners to automatically scale down to zero when our remote team is not actively pushing code?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
GitLab Runner autoscaler idle_count 0 scale to zero Docker Autoscaler executor official docs Google ↗
GitLab Runner Kubernetes executor scale node pool to zero cluster autoscaler official docs Google ↗
- Docker Autoscaler executor · docs.gitlab.com
- GitLab Runner Autoscaling · docs.gitlab.com
- Advanced configuration · docs.gitlab.com
- Kubernetes executor · docs.gitlab.com
- gitlab-runner/docs/executors/kubernetes/_index.md at main · gitlabhq/gitlab-runner · github.com
- Docker Machine Executor autoscale configuration · docs.gitlab.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
GitLab Runner autoscaler idle_count 0 scale to zero Docker Autoscaler executor official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
GitLab Runner Kubernetes executor scale node pool to zero cluster autoscaler official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |