chore(tra-976): AKS burndown — deprovision Azure demo cluster - #156
Merged
Conversation
Destroyed the stopped AKS demo stack to stop the ~$40/mo Azure run rate (Standard LB + 2 static IPs + ACR bill even while compute is halted). GKE is the forward bet; AKS stays a contingency/portfolio target, rebuildable via `just azure`. Live teardown (terraform/azure, *.tf left intact): - state rm'd azurerm_dns_zone.aks_trakrf_app + azurerm_resource_group.main so the destroy preserves the aks.trakrf.app delegation zone and its RG container (Azure DNS zones can't exist outside an RG — unlike Route53). - apply -destroy removed 22 resources: AKS cluster, ACR, Traefik static PIP, vnet/nsg/subnet, cert-manager + CI user-assigned identities, all role assignments, the azuread CI app/SP/groups/federated creds, and the two A records. MC_ node RG auto-deleted with the cluster. - Verified: only the aks.trakrf.app zone remains; nameservers unchanged (no NS rotation), NS + SOA still resolve through the Cloudflare delegation. On rebuild the zone + RG re-import cleanly. Docs: reframe AKS "stopped" -> "deprovisioned" in README (mirrors the EKS treatment) and the argocd-image-updater GKE-only comment. 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
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.
What
Burned down the stopped AKS demo stack (TRA-976) to stop the ~$40/mo Azure run rate, preserving the
aks.trakrf.appDNS delegation zone. Mirrors the 2026-04-21 EKS burndown. GKE is the forward bet; AKS stays a contingency/portfolio target, rebuildable viajust azure.A stopped cluster bills ~$25/mo for a Standard load balancer + 2 static IPs fronting a cluster nobody can reach, plus ~$5 ACR and small disks — pure waste for a parked asset.
Live teardown (already executed —
terraform/azure/*.tfleft intact)state rmofazurerm_dns_zone.aks_trakrf_appandazurerm_resource_group.mainso the destroy preserves the delegation zone and its RG container. (Azure DNS zones can't exist outside an RG — unlike Route53, so the RG must survive too.)apply -destroyremoved 22 resources: AKS cluster, ACR, Traefik static PIP, vnet/nsg/subnet, cert-manager + CI user-assigned identities, all role assignments, the azuread CI app/SP/groups/federated creds, and the two A records. TheMC_node resource group auto-deleted with the cluster.Verification
MC_resource group goneprevent_destroyguards restored in code)This PR's diff
Docs-only — reframes AKS stopped → deprovisioned:
README.md— intro, multi-cloud rationale, repo tour, cost, status sectionsargocd/root/templates/argocd-image-updater.yaml— GKE-only commentThe dated design spec under
docs/superpowers/specs/keeps "AKS stopped" intentionally (historical point-in-time record).🤖 Generated with Claude Code