Project reference ↗

Containerized databases need persistent volumes that remain available as applications move or worker machines fail. StorageOS, later known as Ondat, provided a distributed storage layer for that purpose, integrating with container platforms through their storage interfaces. The company was acquired by Akamai, but that fact does not establish a supported path for an inherited standalone deployment. Preserve volume identities, keys and recovery options before changing controllers: a common storage API does not make the underlying data interchangeable between products.

Current guidance

This record identifies StorageOS’s distributed container storage, later known as Ondat. The linked original chart repository explicitly says it is no longer maintained and points to a separate chart repository. Akamai’s 2023 annual filing confirms it acquired StorageOS, also known as Ondat, in March 2023 to strengthen its cloud computing offerings. A completed acquisition does not establish a current compatibility matrix, standalone product support promise or documented conversion path from an existing StorageOS cluster to a different CSI driver.

An inherited installation needs an inventory of volumes, replicas, node devices, encryption keys, storage classes and the control-plane dependencies that hold its metadata. Do not uninstall the storage controller, change reclaim policies or remove node data while applications still depend on those volumes. A CSI interface standardizes operations; it does not make the underlying on-disk data portable between vendors.

The next step is to establish the applicable support position with the current vendor and prove an independent recovery path. For a replacement, use application-aware export/restore or a documented cross-storage migration, with checksums and workload validation on the target. Keep the original storage available through the rollback window. No primary source reviewed here demonstrated a supported in-place successor, so this entry remains unverified for new standalone adoption.

Historical upstream link check · 2026-10-09

The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub marks storageos/helm-chart as archived. This confirms the repository's read-only archive state; any successor or supported distribution needs separate evidence. Link availability does not certify the historical installation instructions or current security support.

Source for this check ↗

Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.

The original record

Historical Kubedex content

Original publication: 2018-09-22T08:41:59+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.

StorageOS is cloud native, persistent storage for containers. Benefit from application-centric container storage that moves with your application.

StorageOS makes it easy to build stateful containerized apps with fast, highly available persistent storage. Enterprises benefit from the same policy management and compliance features expected in traditional enterprise storage solutions.

Built to run with any stateful application, on any infrastructure with any orchestrator and as a container, StorageOS easily integrates with your favorite platforms – Kubernetes, OpenShift or Docker and fully implements the Container Storage Interface (CSI).

The post StorageOS appeared first on kubedex.com.

Sources & further reading

  1. Akamai’s Ondat acquisition direction
  2. Historical StorageOS chart repository
  3. Akamai 2023 Form 10-K: completed StorageOS acquisition
  4. Recovered historical source

Spotted something that needs another look?

Help improve this page →