Finish the railiance01 Argo CD declaration workplan.
Assistant: grok Assistant-Session: 01a0d25d-d358-7e13-b84a-d007fbb7e34f
This commit is contained in:
parent
7027f13178
commit
47c3bfa39a
1 changed files with 7 additions and 4 deletions
|
|
@ -4,12 +4,12 @@ type: workplan
|
|||
title: "Declare Argo CD Core on railiance01 and bound its resources"
|
||||
domain: financials
|
||||
repo: railiance-enablement
|
||||
status: active
|
||||
status: finished
|
||||
flavor: implementation
|
||||
owner: codex
|
||||
topic_slug: railiance
|
||||
created: "2026-09-21"
|
||||
updated: "2026-09-21"
|
||||
updated: "2026-09-24"
|
||||
related:
|
||||
- ArchitectureBlueprint-5.6
|
||||
- RPF-WP-0043
|
||||
|
|
@ -89,6 +89,9 @@ is empty.
|
|||
|
||||
## Not in this workplan
|
||||
|
||||
Phase B (AppProjects, root app, per-application adoption) and phase C
|
||||
(retire coulombcore's ArgoCD) each need their own founder go-ahead.
|
||||
Phase B is `RPF-WP-0044` in railiance-platform. Phase C (retire coulombcore's
|
||||
ArgoCD) stays with that later plan. Both need their own founder go-ahead.
|
||||
Once phase B exists, ArgoCD's own manifest should move under GitOps too.
|
||||
|
||||
Both tasks here are done. The install is declared, and the resource bounds
|
||||
were applied on 2026-09-21.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue