Record verified scheduler CI and confirmed Argo readiness

This commit is contained in:
dingo
2026-09-19 19:12:28 -04:00
parent b620edfd6f
commit be4382472c
3 changed files with 22 additions and 9 deletions
+8 -5
View File
@@ -7,8 +7,10 @@ broader checks and a bounded **stateless proof Job**. It is not a region server.
Cluster execution must be recorded separately from image publication.
The expanded [run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402)
passed all checks and published `4c2cc04`. The dev Kustomize manifest already pins
that verified image digest. Argo bootstrap examples still need the actual
passed all checks and published `4c2cc04`. The maintainer's later GitOps commit
`20e609d` pins the verified run 1399 image instead; M1.6 preserves that selection.
The maintainer confirms Argo is ready to pick up deployment additions. Bootstrap
examples still need the actual
application namespace and destination; do not apply examples unchanged.
## Gitea and Harbor
@@ -59,8 +61,9 @@ instrumentation, not future concurrency. Record actual results in VALIDATION.md.
## Argo settings and promotion
Reuse the maintainer's application once its GitOps source is confirmed. For an
application watching this repository directly:
Reuse the maintainer's confirmed application. The following are bootstrap
settings for an application watching this repository directly, not an inspection
of the live application's configuration:
| Field | Value |
|---|---|
@@ -81,7 +84,7 @@ Before syncing:
1. Wait for successful checks and publication of the intended commit.
2. Update `deploy/kubernetes/dev/kustomization.yaml` to the published
`sha256:<64 hex>` digest, review and commit it. It currently pins run 1402;
`sha256:<64 hex>` digest, review and commit it. It currently pins run 1399;
no floating tag or fallback image is used.
3. Run `kubectl kustomize deploy/kubernetes/dev`. Check exactly three resources,
all in evolution-dev, the selected digest and no unresolved marker.