AWS / Azure-AKS / EKS cloud-deploy build history #221
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!221
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/aws-eks-build-history"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What this is
docs/ops/aws-eks-build-history.md— the trail of problems hit and fixes made while standing up the cloud-deploy paths. Not a current-state audit; this is how the build actually went.Synthesized from four sources: the git commit history, the closed PRs, the in-repo build notes (
GATE-NOTES.md,aks-cost-experiment.md,deploy/eks/UPGRADE.md,deploy/README.md), and the leftover germination run logs (germinate-aks-poc*.log,mirror-run2.log). Every entry cites its commit sha and/or PR number.Shape
Three tracks, with the inheritance chain called out (a lot of AWS/EKS behavior was fixed on the AKS path first and carried over):
set -u/ nix locale / Docker ≥28 raw-table DROP), the turnkey one-command IaC (#120), zero-DNSDOMAIN=auto+ report-home (#132), gzip user-data for the EC2 16 KB cap.mode=aks+trim_gitops_aks(#139); the full azure-gate CI saga (#143→#159, incl. the cert-zone-doubling bug that never issued certs); the coredns/mirror/CNPG/storageClass bundle (#162/#167/#178/#183/#187/#188); and the AKS cost experiment with its pile of hard-wonazgotchas (CNPG PDBs blocking drains, B-v2 quota 0,nodepool addclient crash →az rest, the CNPG image-redirect restart-loop, the 12-disk attach limit).trim_gitops_eks; plus the operational rules fromUPGRADE.md(version-drift billing trap,--forcenode roll past CNPG PDBs). Note EKS has no merged PRs — code-complete but ran out-of-band, which is whydeploy/eks/is still untracked.A closing section traces which build-era through-lines are still open.
🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.