revert: CF migration (operator pivoted back to DO k8s)#35
Merged
Conversation
mastermanas805
added a commit
that referenced
this pull request
Jun 5, 2026
…) (#54) Companion to worker #35 (failover ESP provider). Rule 25 — every new metric ships its alert + dashboard tile + catalog row. Metric: instant_email_failover_total{outcome} emitted by the worker FailoverProvider (worker/internal/email/failover_provider.go). Inert when EMAIL_PROVIDER_FALLBACK is unset (lazy CounterVec, never emits in single-provider mode). - prometheus-rules: new instant-worker-email-failover group — EmailFailoverEngaged (P1, fallback_ok rate > 0 for 10m = primary ESP degraded, secondary carrying load) and EmailFailoverAllFailed (P0, all_failed rate > 0 for 5m = every ESP refused, email being lost). - newrelic/alerts: email-failover-engaged.json (P1), email-failover-all-failed.json (P0). Mirror the Prom thresholds. - dashboard: "Email failover outcomes (1h)" line tile faceted by outcome. - METRICS-CATALOG: row for instant_email_failover_total (lazy, owner worker, alerts + tile cross-referenced). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Operator pivoted 2026-05-30: keeping DO k8s for staging, abandoning Cloudflare Containers. Reverts all 3 CF migration PRs: #32 (TF bootstrap + wrangler scaffold + 5 workflows), #33 (TTL=1 + Global Key env vars), #34 (drop cache.tf + nudge).
Removes 2585 lines / 47 files. Specifically:
terraform/cloudflare/(13 files): tokens, R2, DNS, Pages, variables, Makefile, READMEwrangler/(~30 files): 8 service subdirs + top-level README + package.json + node_modules-as-dep.github/workflows/terraform*.yml(3 files): plan + per-env apply.github/workflows/wrangler-*.yml(2 files): build + deployBug-burner workflow changes + k8s manifests + NR alerts unaffected.
Companion PRs (revert sequence)
instanodedev/api#???(revert :staging tag + notify-infra-on-migration.yml)instanodedev/worker#???(revert :staging tag)instanodedev/provisioner#???(revert :staging tag)What remains for operator cleanup (NOT in this PR)
instanode-web-staging), 1 Pages custom domain (staging.instanode.dev), 2 R2 buckets (instanode-tf-state,instant-shared-staging), 6 GH repo secrets (CLOUDFLARE_, CF_ACCOUNT_ID, TF_STATE_R2_)Test plan
🤖 Generated with Claude Code