S3 Platform Services — PostgreSQL HA, Valkey, object storage
28f445fa89
The 2026-08-11 decision to keep ArgoCD rested on a claim that turned out to be wrong. Verified against both clusters once API access was restored: ArgoCD is not on railiance01, it runs on CoulombCore, its Applications target CoulombCore in-cluster, nothing on railiance01 is ArgoCD-managed, and the live S3 workloads - target-revenue, openbao, external-secrets - deploy outside GitOps. Two Applications are Degraded and one is OutOfSync/Missing. The earlier claim that removing ArgoCD documentation would describe a system that does not exist was backwards: the documentation already describes a deployment path that is largely not in effect. Restates the question with three real options - adopt properly on railiance01, retire, or relocate to Helix Forge - and notes that doing nothing is the option with a cost. Same defect class as RAIL-HO-WP-0009: declared and live state diverged, and nothing detected it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| argocd | ||
| credential-change-requests | ||
| credential-grants | ||
| docs | ||
| helm | ||
| history | ||
| lib | ||
| openbao | ||
| registry | ||
| schemas | ||
| scripts | ||
| tests | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| ArchitectureBlueprint.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||