docs: plan node-independent akh-platform storage (PR 0/9) #651
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/platform-storage-design-20261015"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The platform still depends on node-local PVCs even though current main already supports Postgres for runtime, session, event and core operation records. This docs-only design classifies durable state, identifies file-only session secrets and cognitive workspace caches, and defines verified import, rollback and cross-node acceptance gates.
This is PR 0/9, the documentation prerequisite. Operator authorization covers PRs 1–6 only, one at a time after the preceding PR is reviewed and merged by the operator. PRs 7–9 require the disposition ledger and a separate GO. No code, manifests, production state or workload behavior changes are included.
The plan coordinates with Talos #208 and the #212 staging receipt, reusing existing ESO stores/database delivery and roles. PR 6 must remain inert and stop with a documented conflict if it overlaps the houses registry or placement.
Validation: git diff --check and all relative documentation links pass. Source, backup metadata/hash and read-only cluster observations are dated in the note; these are not import or relocation acceptance. Repository CI is pending at submission.
No deployment, data import, volume switch, Board use or credential output. Please review and merge this docs prerequisite before PR 1 begins.