NetApp announced Project Astra in April 2020 as an initiative to bring enterprise-class storage services to Kubernetes, addressing one of the most commonly cited barriers to widespread enterprise adoption of container orchestration: the lack of persistent, portable storage for stateful applications.
The Problem: Stateless Containers in a Stateful World
Kubernetes has become the dominant orchestrator for containerized applications, prized for its portability and scalability. However, containers are fundamentally stateless by design. When an application with a database dependency is moved between environments—whether shifting across clouds or transitioning from on-premises infrastructure to a public cloud provider—data portability becomes a serious operational challenge.
Every time a container starts, it must re-establish a connection to its underlying data store. As workloads move, the data must follow—reliably, consistently, and with enterprise-grade guarantees around backup, recovery, and availability. Without a coherent solution for this, enterprises face significant risk when running stateful workloads such as databases or file-dependent applications in containerized environments.
“Kubernetes is becoming ubiquitous as an orchestrator for container applications. It is focused on portability. But the biggest block to adoption by enterprises today is that containers are stateless, and portability of the data is lost.”
Beth Busenhart, Market Strategist, NetApp
What Is Project Astra?
Project Astra is a storage and container platform built on Kubernetes. At the time of its announcement, it was described as a forward-looking initiative rather than a finished product—an alpha demonstration of NetApp’s vision for how enterprises can manage applications and data as they move between on-premises and multi-cloud environments.
Key design goals for Project Astra included:
- Kubernetes-agnostic deployment: Rather than locking customers into a proprietary Kubernetes distribution, Project Astra was designed to integrate with any Kubernetes service a customer already uses.
- Storage-agnostic architecture: The platform was intended to work across multiple storage backends, avoiding vendor lock-in.
- Multi-cloud and on-premises support: Initial focus was on the three major public clouds—Google Cloud Platform, Microsoft Azure, and Amazon Web Services—with on-premises support also planned.
- Enterprise storage services for containers: Capabilities such as data snapshots, backups, cloning, migration, and storage efficiency features were targeted to make Kubernetes more workload-friendly for production use cases.
Departure from NetApp Kubernetes Service (NKS)
Project Astra represented a strategic pivot from NetApp’s earlier offering, NetApp Kubernetes Service (NKS). NKS was a proprietary managed Kubernetes distribution that competed in a crowded market alongside services such as Google Kubernetes Engine (GKE) and Red Hat OpenShift.
NetApp signaled it would wind down NKS around the same time Project Astra was announced. The distinction is important: where NKS provided a single control plane for Kubernetes across cloud platforms, Project Astra shifted focus toward enabling application and data portability across any Kubernetes environment rather than building and maintaining a competing distribution.
“The big difference between NKS and Project Astra is that Project Astra allows customers to bring data and workloads on their portability journey.”
Beth Busenhart, NetApp
Trident: The Open Source Foundation
A key technical building block for Project Astra is Trident, NetApp’s open source dynamic storage provisioner for Kubernetes. Trident enables Kubernetes to provision and manage persistent volumes backed by NetApp storage systems.
Trident was to remain available as a standalone open source project while also being incorporated into the Project Astra platform, giving enterprise users an integrated experience on top of the open source foundation.
Integration with NetApp’s Data Fabric Strategy
Project Astra fits into NetApp’s broader Data Fabric strategy, which is centered on enabling seamless data movement across on-premises infrastructure, private clouds, and public cloud services. The Data Fabric approach is intended to give enterprises consistent data management capabilities regardless of where data and workloads reside.
This also connects to NetApp Keystone, announced in October 2019, which provides a consumption-based model for on-premises and cloud storage, allowing customers to migrate data across environments without committing upfront to a fixed infrastructure footprint.
Industry Context: Why Persistent Storage in Kubernetes Matters
John Woodall, Vice President of Engineering West at General Datatech (a Dallas-based NetApp channel partner), drew a comparison between the potential impact of Project Astra and what VMware did for x86 virtualization. Before VMware popularized virtualization for Windows and Linux workloads, virtualization was largely confined to mainframe environments. VMware’s platform brought enterprise-grade resource management—snapshots, live migration, HA clustering—that transformed how data centers operated.
Woodall argued that a similar transformation is underway with containers, and that the missing piece has been persistent, portable data management:
“If I can combine backup and recovery, easy migration and portability, cloning, and storage efficiency technologies, I’ve added value to make Kubernetes more workload-friendly.”
John Woodall, VP Engineering West, General Datatech
The analogy highlights that container orchestration platforms alone do not provide the full operational toolset that enterprises expect—particularly around data protection, disaster recovery, and workload mobility at scale.
Release Timeline (as of April 2020)
At the time of the announcement, NetApp outlined the following rollout schedule:
- April 2020: Alpha preview for a select group of customers and channel partners.
- Summer 2020: Beta release planned for broader customer testing.
- Fall 2020: General availability target.
Note that these timelines reflect what was communicated at announcement. Readers researching the current state of this product should consult NetApp’s official documentation, as Project Astra has since evolved—NetApp subsequently launched Astra Control as the generally available product based on this initiative.
Key Takeaways for DevOps and Platform Teams
- Persistent storage for stateful Kubernetes workloads remains a genuine operational challenge in multi-cloud and hybrid deployments.
- NetApp’s approach separates storage management from Kubernetes distribution choice—teams are not required to adopt a specific Kubernetes flavor.
- Trident, as an open source CSI-compatible provisioner, is a practical starting point for teams evaluating NetApp storage integration with Kubernetes today.
- The Data Fabric and Keystone initiatives suggest NetApp is positioning itself for long-term hybrid and multi-cloud storage management, not just on-premises storage.
- For enterprises running stateful workloads—databases, message queues, file-dependent services—evaluating persistent volume solutions with enterprise data services (backup, snapshot, clone) is important before moving those workloads to production Kubernetes environments.