Skip to content
runnerhut
Start building

Argo CD

Argo CD CI on GitHub Actions

Deployment jobs poll for sync status and burn CI minutes waiting.

−75%
Runner cost while waiting

Deployment jobs poll for sync status and burn CI minutes waiting.

Why it happens

The workflow blocks on a sync that Argo CD performs asynchronously.

What to change

  1. Trigger the sync and exit; let Argo CD report status back via a webhook
  2. If you must wait, poll with a timeout on a 2 vCPU runner rather than a large one
  3. Separate image build from manifest update so a slow rollout does not block builds

Argo CD on runnerhut

yaml
jobs:
  deploy:
    runs-on: runnerhut-2vcpu-ubuntu-2404
    steps:
      - uses: actions/checkout@v4
      - run: argocd app sync api --grpc-web
      - run: argocd app wait api --timeout 300 --grpc-web
A working starting point

The only runnerhut-specific line is `runs-on: runnerhut-2vcpu-ubuntu-2404`. Everything else is standard GitHub Actions — the same actions, the same secrets and the same permissions model you use today.

Your next build could be twice as fast, at half the price

Start free. Migrating away is the same one line, and we publish that diff too.

Start buildingSee pricing

Related

Terraformterraform init downloads every provider on every run.PulumiPlugin and dependency installation runs before every preview.KubernetesSpinning up a kind or k3s cluster takes minutes before tests start.HelmChart dependency updates and linting run cold every time.