Public: anyone can read this; nobody can change it.

azure-gate: real-cloud CI gate on Azure (vms + aks), manual-dispatch #143

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

Adds a manual-dispatch workflow that deploys a real mitosis platform on Azure, tests it end to end (germinate → cold-start assertions → build a canary app and follow it preview→merge→prod), then destroys everything. Two grounds, chosen per run.

Notes

shipped merged

opened this view on origin

Adds a manual-dispatch workflow that deploys a real mitosis platform on Azure, tests it end to end (germinate → cold-start assertions → build a canary app and follow it preview→merge→prod), then destroys everything. Two grounds, chosen per run. Merging this is what makes it appear in Actions → azure-gate → Run workflow (Forgejo only lists dispatch workflows that live on the default branch).

What's here

  • deploy/azure/gate.sh — one entrypoint, laptop == CI. SP or az login auth, RG-per-run (mitosis-gate-<run>, tagged purpose/run/ref/expires/mode for Cost Analysis + the janitor), teardown on any exit, --keep, --janitor.
    • vms: main.bicep mode=vms domain=auto (sslip.io → zero DNS); leader germinates, the gate watches + asserts over SSH. ~$0.30, ~1h.
    • aks: main.bicep mode=aks + a per-run Azure DNS zone <run>.gate.open-platform.sh delegated in Cloudflare; germinates locally (CLUSTER_PROFILE=aks), writes the edge A records when the LB IP appears, asserts with GROUND=aks. ~$1–2, ~2h.
  • scripts/coldstart-assert.sh — NODE_MODE=local (bare-VM A5 probes the host, not a k3d container) and GROUND=aks (skips A5; lower Flux-Kustomization floor; A9-grafana self-skips). k3s/k3d path byte-identical when both are unset — this PR's coldstart run proves that.
  • .forgejo/workflows/azure-gate.yml — workflow_dispatch (mode/keep/e2e/ssh_pubkey) + a nightly janitor that reaps expired gate RGs + an if: always() RG safety net. No PR/push trigger (each run spends real money).
  • Docs: README "Run it yourself" + docs/ops/coldstart-ci.md + deploy/azure/GATE-NOTES.md (build log / handoff, incl. the identity, secrets, DNS design, and gotchas).

Proof

  • vms: PROVEN green on real Azure — full cold-start gate A1–A12 passed (incl. bare-VM A5); app-E2E validated on the same run.
  • aks: under live validation right now — DNS delegation proven end-to-end and torn down clean; a full aks run (deploy → delegate → mirror → germinate → assert → e2e → destroy) is in flight. aks is opt-in and self-cleaning; any issue found lands as a fix-forward. The known open risk is the CNPG restart-loop from aks-cost-experiment.md (extend aks-image-redirect to the CNPG Cluster spec) — will surface at the aks e2e step.

Ops

Repo secrets already set: AZURE_GATE_{CLIENT_ID,CLIENT_SECRET,TENANT_ID,SUBSCRIPTION_ID} (SP mitosis-azure-gate, Contributor), AZURE_GATE_CLAUDE_TOKEN (crew credential for the E2E), AZURE_GATE_CF_TOKEN (Cloudflare, aks DNS). cf-token at repo root is gitignored.

🤖 Generated with Claude Code

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs