Ondat, the Kubernetes-native data platform provider, has released version 2.8 of its Ondat platform for stateful workloads in Kubernetes. The new version brings significant changes that open up the option of running a robust ETCD setup within production clusters, removing the need for external service setup. This change reduces operational overhead and cost for production users.

Snapshots provide additional confidence in the safety of user data. Snapshots can be used with other backup and disaster recovery services to create backups of your data outside of the cluster (i.e., in AWS S3 backups) for audit, disaster recovery and regulatory compliance. These backups can be used to restore applications to a known state, create ad-hoc clones of applications at a chosen point in time or to keep a backup application instance up to date with the newest data to help make any failover as non-disruptive as possible.

ETCD clusters can now run within Kubernetes itself. This reduces costs by eliminating the need to run ETCD—a highly-available key value store for cluster data in Kubernetes—in separate compute instances. At the same time, it lowers operational burdens and increases agility for developers. Most container-native storage solutions still require ETCD to run outside the cluster for production workloads, and Ondat is among the first to deliver this important capability.

Prometheus endpoints are now supported. Ondat 2.8 provides information around the disks and filesystems underpinning each volume on every node, and the information includes key metrics that can trigger alerts should anything occur that demands attention, allowing users to stay ahead of any potential problems.

The metrics provided will help users analyze a cluster’s utilization and performance and drive improvements. A user’s Prometheus instance needs only to communicate with a single endpoint where data for all Ondat volumes will be collated and presented.