Historical record: 3.0 working POC

Documentation home · Current support scope

This page describes the original 3.0.0 rewrite milestone released on 25 October 2026. It is historical context, not current installation guidance or a pending qualification plan. Later 3.x releases extended its file, handle, membership and credential behavior.

What the milestone introduced

The rewrite separated manager, node replication controller, replica worker and CSI/FUSE responsibilities. It used ordinary local-CSI backing PVCs and fixed creation-time replica counts from one through four. Raft ordered mutations and read barriers; journals and checksummed full-history baselines preserved original member authority through restart and catch-up.

Lifecycle reconciliation recorded original PVC/Node/backing identities and activation/exposure state. Durable deletion fences, unavailable-node cleanup blockers, Retain preservation and complete-runtime removal/reinstall were part of its recorded operating scope. Structured logs and bounded operational metrics made failures inspectable.

Original limitations and subsequent changes

The POC did not promise a general application/POSIX filesystem. Its early append, permissions, link, handle-reclamation, current-state checkpoint, replacement and credential limitations must not be applied to the present implementation. Use filesystem semantics, replication and security for current behavior.

The literal single-node milestone was deferred at the 3.0 release and later recorded using published 3.2.0 images. That later observation does not rewrite 3.0's original evidence. Host power loss, arbitrary disk failure, unrestricted history, retired-driver migration and production availability were not established by the POC.

Source-bound record

The original POC exit report retains exact sources, outcomes, failed attempts and deferrals. The executable harnesses referenced by old reports have been removed; their earlier versions remain in Git history. There is no instruction to recreate or run them here.