Deliver the platform layer and store Jobs through Argo CD
At the maintainer's request everything but Secrets and the store node label now goes through Argo CD. aevolution-platform syncs one bundle (World0 admission policy, Retain storage class, each environment's namespace, guardrails, service accounts and object claim) with self-heal, no prune and Prune=false,Delete=false on every object; the admission policy also protects the platform app and project. Store Jobs become kustomize components used as PreSync (migrate) and PostSync (check-store) hooks per environment, and the policy check refuses any unresolved marker in a path an Application syncs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -2757,3 +2757,27 @@ admission policy and the stage and World0 AppProjects, then ran
|
||||
file.
|
||||
- PostgreSQL Release and ASan/UBSan passed. The analysis build passed after one
|
||||
loop copy was fixed. Deploy policy: 0 failures.
|
||||
|
||||
## M8.3 Argo delivery - 2026-09-29
|
||||
|
||||
- The platform layer is now `deploy/kubernetes/platform/cluster`, delivered by the
|
||||
`aevolution-platform` Application. It renders 29 objects, all marked
|
||||
`Prune=false,Delete=false`: 3 namespaces, 3 quotas, 3 limit ranges, 6 network
|
||||
policies, 9 service accounts, 2 claims, the storage class, the policy and its
|
||||
binding.
|
||||
- The store Jobs are kustomize components used as Argo hooks. The dev overlay
|
||||
renders into `evolution-dev` with PreSync and PostSync hooks; its digests and
|
||||
role are still markers.
|
||||
- `deploy-policy-check.py`: 43 objects in 41 files, 0 failures. Five new mutations
|
||||
were each caught:
|
||||
- platform prune enabled;
|
||||
- a missing Delete guard;
|
||||
- an unfinished stores overlay included in the live dev path;
|
||||
- an extra cluster kind in the platform project;
|
||||
- the admission policy no longer covering the platform app.
|
||||
The unfinished-path rule first missed the live dev Application, which exists
|
||||
here only as an `.example`. It now covers every Application whose path is
|
||||
resolved.
|
||||
- The digests the maintainer pasted are local image IDs from the build step, not
|
||||
registry digests. The registry digest is printed by the Publish step.
|
||||
- Not executed: bootstrapping the platform Application, or any Argo sync.
|
||||
|
||||
Reference in New Issue
Block a user