Plans index
One line per plan, with where it stands. “Done” means built and merged; “superseded” names what replaced it. Plans are working documents: they record decisions and the reasoning at the time.
The current work is at the top.
Current (V4.0.0-pre)
| Plan |
Status |
What it is |
| v4-production-cutover.md |
plan, nothing executed |
moving V4 to production (blue/green), V3 retired and kept as source |
| v4-documentation-update.md |
in progress |
the documents for the pre-release: READMEs, data terms, guides, hygiene |
| ingress-source-address-fix.md |
to be done by the cluster administrator |
the ingress hides callers’ addresses, so the per-address limit is shared by everyone; the fix (externalTrafficPolicy: Local), its checks and rollback |
| git-history-cleanup.md |
not done (a runbook for the owner) |
rewriting the Git history to remove internal names |
| v4-sizing-test.md |
done |
replica shapes compared on the cluster; the decision (20 x 1000m) |
| v4-staging-rollout.md |
done for staging |
Kubernetes, manifests and scripting for the staging environment (its script parts are superseded by v4-staging-scripts) |
| v4-staging-scripts.md |
done |
the deploy and secret-sealing scripts and their conventions |
| v4-release-to-staging.md |
largely done |
the steps from “feature complete” to running on staging |
| v4-results-report.md |
to be extended |
V3 versus V4, the clean-run comparison; the performance report will combine it with the cluster and soak results |
| v4-deployment.md |
partly done |
image, secrets, environments and the cluster (the design behind the staging work) |
| v4-initial-release-roadmap.md |
tracking checklist |
the path to an initial release |
| onprem-k8s-migration.md |
done |
the move from Azure to the on-prem cluster; also the cluster’s DNS and certificate notes |
V4 features (built)
Background and history