Skip to content

ci: run jobs on the on-prem self-hosted-linux ARC pool - #32

Merged
mattmattox merged 3 commits into
mainfrom
ci/runners-on-prem-hosted
Sep 19, 2026
Merged

mattmattox merged 3 commits into
mainfrom
ci/runners-on-prem-hosted

Conversation

@mattmattox

Copy link
Copy Markdown
Contributor

Moves this repo's GitHub-hosted (ubuntu-latest / ubuntu-24.04) and retired [self-hosted, bare-metal] jobs onto the on-prem ARC pool (self-hosted-linux).

Why (owner decision 2026-09-19): every project's CI runs on the on-prem cluster.

  • The DFW Spot CI cluster is being retired.
  • Private repos stop spending paid Actions minutes.
  • The bare-metal host runners haven't taken a job since 2026-08-08 and are being retired.

The pool: evenly spread over a1ubaip01 + four R720s. It runs DinD with a Docker daemon (DOCKER_HOST) and RAM-tmpfs scratch, and requests 3 CPU per runner so jobs queue instead of oversubscribing hosts. The image bakes helm, kubectl, gitleaks, node, go and python3. Its tool set differs from GitHub's ubuntu-latest, so a job that assumed a preinstalled tool may need a setup-* step. This PR's own CI is the check.

Fork PRs: outside contributors' workflows need maintainer approval in both orgs (all_external_contributors).

Rollback: revert this PR.

No-Task: move all CI onto the on-prem cluster (cluster-services, 2026-09-19)

Moves GitHub-hosted (ubuntu-latest/24.04) and retired bare-metal jobs onto
the on-prem pool; the DFW CI cluster and the idle host runners are retired.

No-Task: move all CI onto the on-prem cluster
…nner

The self-hosted-linux image has no zip, so the windows leg died with
'zip: command not found' and fail-fast cancelled the other four legs.
Also disable setup-go's cache: the runner's GOCACHE/GOMODCACHE are a
shared hostPath and the post-step spent 6+ min tarring it.

No-Task: move all CI onto the on-prem cluster
GOCACHE/GOMODCACHE already live on the runner's persistent shared /cache;
setup-go's cache step only re-archives it in the post-job step (measured
6-27 extra minutes per job), so set cache: false on every setup-go step.

No-Task: move all CI onto the on-prem cluster
@mattmattox
mattmattox merged commit caa7891 into main Sep 19, 2026
11 checks passed
@mattmattox
mattmattox deleted the ci/runners-on-prem-hosted branch September 19, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant