pdurlej/platform

Fork 0

meta(upgrades): plan staged module upgrade waves after metadata and DR #389

New issue

Closed

opened 2026-05-19 08:54:45 +02:00 by codex · 4 comments

codex commented

2026-05-19 08:54:45 +02:00

Collaborator

Scope

Coordinate W8 module upgrade waves after ADR-0022 source/artifact metadata and DR confidence. This is a planning/decomposition lane, not an upgrade execution issue.

Current source artifacts

PR #466: docs(w8): prepare staged module upgrade plan
state/cycle/W8-module-upgrade-prep.md after #466 merges
state/roadmap/forgejo-upgrade-plan.md after #466 merges
decisions/0022-module-source-and-release-boundaries.md
state/roadmap/current-platform-roadmap.md

W8 sequencing

W8.0 readiness: metadata/source/artifact inventory and risk classification; repo-only.
W8.1 pilot: lowest-blast upgrade candidate, default minio-init; no Forgejo first.
W8.2 low-risk apps: standard/maintenance app upgrades after pilot.
W8.3 stateful/sidecar: backup-before and rollback evidence required.
W8.final core/workbench: Forgejo and core services after pilot + DR stance.

Acceptance criteria

Classify candidates by source/artifact/update policy.
Separate core/stateful/public-edge/auth/security-sensitive upgrades from low-risk upgrades.
Define smoke, backup, and rollback evidence per class.
Make Forgejo a dedicated later plan, not the first upgrade.
Open child issues only when the target module has enough metadata and rollback evidence to be agent-ready.

Out of scope

Running upgrades directly from this issue.
Changing production images.
Applying/recreating services.
Broad repo splits.

Current next step

Merge/review PR #466, then create proposed child issues for W8.0 metadata readiness and W8.1 pilot selection.

## Scope Coordinate W8 module upgrade waves after ADR-0022 source/artifact metadata and DR confidence. This is a planning/decomposition lane, not an upgrade execution issue. ## Current source artifacts - PR #466: `docs(w8): prepare staged module upgrade plan` - `state/cycle/W8-module-upgrade-prep.md` after #466 merges - `state/roadmap/forgejo-upgrade-plan.md` after #466 merges - `decisions/0022-module-source-and-release-boundaries.md` - `state/roadmap/current-platform-roadmap.md` ## W8 sequencing - W8.0 readiness: metadata/source/artifact inventory and risk classification; repo-only. - W8.1 pilot: lowest-blast upgrade candidate, default `minio-init`; no Forgejo first. - W8.2 low-risk apps: standard/maintenance app upgrades after pilot. - W8.3 stateful/sidecar: backup-before and rollback evidence required. - W8.final core/workbench: Forgejo and core services after pilot + DR stance. ## Acceptance criteria - Classify candidates by source/artifact/update policy. - Separate core/stateful/public-edge/auth/security-sensitive upgrades from low-risk upgrades. - Define smoke, backup, and rollback evidence per class. - Make Forgejo a dedicated later plan, not the first upgrade. - Open child issues only when the target module has enough metadata and rollback evidence to be agent-ready. ## Out of scope - Running upgrades directly from this issue. - Changing production images. - Applying/recreating services. - Broad repo splits. ## Current next step Merge/review PR #466, then create proposed child issues for W8.0 metadata readiness and W8.1 pilot selection.

codex added this to the 09 - Module upgrade waves milestone

2026-05-19 08:54:45 +02:00

codex added the

proposed

meta

risk/process

labels

2026-05-19 08:54:45 +02:00

codex referenced this issue

2026-05-25 00:49:59 +02:00

docs(w8): prepare staged module upgrade plan #466

codex referenced this issue

2026-05-26 08:51:34 +02:00

chore(w8): refresh module upgrade readiness inventory #501

codex referenced this issue

2026-05-26 08:52:26 +02:00

chore(minio-init): prepare W8.1 pilot upgrade packet #502

codex commented

2026-05-26 08:52:53 +02:00

Author

Collaborator

W8 decomposition update after Oracle review and operator approval (2026-05-26):

#500 closed the stale W6d/#488 platform policy expansion path: Patchwarden owns policy-driven review/automerge; platform remains thin client.
#501 created W8.0 readiness inventory as ready-for-agent, repo-only, no runtime mutation.
#502 created W8.1 minio-init pilot packet as proposed, gated on #501 output and explicit no-apply/no-recreate scope.

Interpretation: #389 remains the M09 coordination lane. Next useful action is #501; #502 should become agent-ready only after W8.0 confirms the candidate metadata and rollback/smoke packet are sufficient.

W8 decomposition update after Oracle review and operator approval (2026-05-26): - #500 closed the stale W6d/#488 platform policy expansion path: Patchwarden owns policy-driven review/automerge; platform remains thin client. - #501 created W8.0 readiness inventory as `ready-for-agent`, repo-only, no runtime mutation. - #502 created W8.1 `minio-init` pilot packet as `proposed`, gated on #501 output and explicit no-apply/no-recreate scope. Interpretation: #389 remains the M09 coordination lane. Next useful action is #501; #502 should become agent-ready only after W8.0 confirms the candidate metadata and rollback/smoke packet are sufficient.

codex referenced this issue

2026-05-26 09:39:07 +02:00

docs(w8): record module upgrade readiness #503

codex referenced this issue

2026-05-26 09:49:16 +02:00

docs(minio-init): prepare W8 pilot packet #504

codex commented

2026-05-26 09:52:18 +02:00

Author

Collaborator

W8 execution update:

#501 closed via PR #503: W8.0 readiness artifact is merged.
#504 is open for #502: W8.1 minio-init pilot packet. It does not upgrade the tag because Docker Hub currently reports the existing minio/mc tag as latest. It pins the desired artifact digest and records smoke/rollback/no-runtime-mutation evidence.
#504 checks are green, but I did not route it through W6d automerge because it touches modules/minio-init/module.yaml; this should remain manual/Iskra-reviewed until Patchwarden owns broader module-metadata lanes.

W8 execution update: - #501 closed via PR #503: W8.0 readiness artifact is merged. - #504 is open for #502: W8.1 `minio-init` pilot packet. It does **not** upgrade the tag because Docker Hub currently reports the existing `minio/mc` tag as latest. It pins the desired artifact digest and records smoke/rollback/no-runtime-mutation evidence. - #504 checks are green, but I did not route it through W6d automerge because it touches `modules/minio-init/module.yaml`; this should remain manual/Iskra-reviewed until Patchwarden owns broader module-metadata lanes.

codex commented

2026-05-26 10:53:47 +02:00

Author

Collaborator

W8.1 pilot packet closed:

PR #504 merged by operator at 2026-05-26 10:52 CEST.
#502 is closed.
Result: minio-init now has desired artifact digest metadata and a W8.1 pilot packet.
No runtime apply/recreate/restart was performed.
Important finding: Docker Hub currently reports the existing minio/mc:RELEASE.2025-08-13T08-35-41Z-cpuv1 tag as latest, so the pilot correctly became digest/evidence pinning, not a fake upgrade.

Next W8 interpretation: W8.0 and W8.1 packet are done. Actual runtime execution or broader module upgrade wave remains separately gated.

W8.1 pilot packet closed: - PR #504 merged by operator at 2026-05-26 10:52 CEST. - #502 is closed. - Result: `minio-init` now has desired artifact digest metadata and a W8.1 pilot packet. - No runtime apply/recreate/restart was performed. - Important finding: Docker Hub currently reports the existing `minio/mc:RELEASE.2025-08-13T08-35-41Z-cpuv1` tag as latest, so the pilot correctly became digest/evidence pinning, not a fake upgrade. Next W8 interpretation: W8.0 and W8.1 packet are done. Actual runtime execution or broader module upgrade wave remains separately gated.

codex referenced this issue

2026-05-26 17:54:21 +02:00

chore(w8.0): fill source/artifact metadata for stateful candidate set #505

codex referenced this issue

2026-05-26 17:54:22 +02:00

chore(uptime-kuma): prepare W8.2 low-risk app upgrade packet #506

codex referenced this issue

2026-05-26 17:54:22 +02:00

docs(w8.3): define stateful and sidecar upgrade gate #507

codex referenced this issue

2026-05-26 17:54:23 +02:00

docs(forgejo): prepare W8.final upgrade preflight packet #508

codex commented

2026-05-26 17:55:28 +02:00

Author

Collaborator

Role: executor
Intent: lane-outcome
Needs owner: no

W8 decomposition after #501/#502 is now split into proposed child issues:

#505 chore(w8.0): fill source/artifact metadata for stateful candidate set — metadata-only for minio, redis, postgres.
#506 chore(uptime-kuma): prepare W8.2 low-risk app upgrade packet — packet only, no runtime execution.
#507 docs(w8.3): define stateful and sidecar upgrade gate — shared backup/rollback/apply gate before W8.3 runtime work.
#508 docs(forgejo): prepare W8.final upgrade preflight packet — Forgejo final-boss preflight only, no upgrade.

All children are proposed, not ready-for-agent, per meta-decomposition discipline. No runtime mutation, no production apply/recreate/restart, no compose/env change.

Spec sources read:

docs/forgejo-agent-operations.md
.forgejo/issue_template/atomic_task.md
.forgejo/issue_template/meta_decomposition.md
state/cycle/W8-module-upgrade-prep.md
state/cycle/W8-readiness-2026-05-26.md
state/cycle/W8-minio-init-pilot.md
state/roadmap/current-platform-roadmap.md
decisions/0022-module-source-and-release-boundaries.md
module manifests/runbooks for uptime-kuma, pogodowa-babcia, forgejo, traefik, honcho-api, minio-init, minio, redis, postgres

Next: operator/orchestrator may mark #505 and #506 ready-for-agent first. #507/#508 should stay proposed until their gates are reviewed because they encode runtime/core policy.

**Role:** executor **Intent:** lane-outcome **Needs owner:** no W8 decomposition after #501/#502 is now split into proposed child issues: - #505 `chore(w8.0): fill source/artifact metadata for stateful candidate set` — metadata-only for `minio`, `redis`, `postgres`. - #506 `chore(uptime-kuma): prepare W8.2 low-risk app upgrade packet` — packet only, no runtime execution. - #507 `docs(w8.3): define stateful and sidecar upgrade gate` — shared backup/rollback/apply gate before W8.3 runtime work. - #508 `docs(forgejo): prepare W8.final upgrade preflight packet` — Forgejo final-boss preflight only, no upgrade. All children are `proposed`, not `ready-for-agent`, per meta-decomposition discipline. No runtime mutation, no production apply/recreate/restart, no compose/env change. Spec sources read: - `docs/forgejo-agent-operations.md` - `.forgejo/issue_template/atomic_task.md` - `.forgejo/issue_template/meta_decomposition.md` - `state/cycle/W8-module-upgrade-prep.md` - `state/cycle/W8-readiness-2026-05-26.md` - `state/cycle/W8-minio-init-pilot.md` - `state/roadmap/current-platform-roadmap.md` - `decisions/0022-module-source-and-release-boundaries.md` - module manifests/runbooks for `uptime-kuma`, `pogodowa-babcia`, `forgejo`, `traefik`, `honcho-api`, `minio-init`, `minio`, `redis`, `postgres` Next: operator/orchestrator may mark #505 and #506 `ready-for-agent` first. #507/#508 should stay proposed until their gates are reviewed because they encode runtime/core policy.

codex referenced this issue

2026-05-26 22:29:50 +02:00

docs(w8): define stateful sidecar upgrade gate #511

codex referenced this issue

2026-05-26 22:30:19 +02:00

docs(forgejo): prepare W8 final preflight packet #512

codex referenced this issue

2026-05-26 23:10:19 +02:00

chore(uptime-kuma): stage W8 desired image update #513

codex referenced this issue from a pull request that will close it,

2026-05-27 08:27:06 +02:00

docs(w8): close uptime-kuma runtime pilot #516