Since the introduction of the modular core in version 2, we have been moving extremely fast. Writing a separate blog post for every provider, plugin, and release update is simply too much. So we decided to start a series of blog posts called OpenEverest Pulse, where we share concise news about providers, plugins, and OpenEverest itself.
OpenEverest 2.0.0-dev.2 release
We shipped OpenEverest 2.0.0-dev.2, the second Developer Preview of v2. This release was a real community effort — 21 external contributors put their time and energy into it. Highlights:
everestctlis now a real day-2 CLI for v2. The whole v2 resource model is drivable from the command line, with consistent--namespace/-n,--wait, and JSON output. New command groups:auth,instance,backup,restore,backup-storage(bs),backup-class(bc), andprovider(prov). Contributed by @VijetaPriya47 through the LFX Mentorship program.- Point-in-time recovery, end to end. PITR is now a first-class part of the v2 model: an authoritative recovery window in status, and
PointInTimeas a proper data source you can use to seed a brand-new instance. - Instance presets. The new
InstancePresetCRD captures a ready-to-use instance shape (provider, version, topology, sizing, storage class) so users can pick a preset instead of filling in a form. - Plugin hub, built in. The v2 UI now ships with a plugin hub by default, so users can discover and find installation instructions right from OpenEverest. The catalog is powered by openeverest/hub — the place where the community and maintainers can publish their own plugins and providers.
- Schema-driven secrets and config maps. Providers declare the secrets and config maps they expect, and the API validates payloads against that schema before they reach Kubernetes.
- Auditable event stream with replay.
GET /v1/eventsno longer drops events across a reconnect — every event carries a sequence and the acting user.
⚠️ Developer Preview — not for production. 2.0.0-dev.2 is not feature-complete and contains breaking changes to every CRD, the HTTP API, and the provider-runtime SDK. There is no upgrade path from Developer Preview 1 or from v1 — install it on a fresh cluster. Installation is Helm-only for this preview. See the release notes for the full breaking-change mapping.
Extension Hub on the website
Thanks to our contributor @amh1k, providers and plugins now show up not only in the OpenEverest Web UI, but also on the website at openeverest.io/extensions.
It lists the extensions added by the community and the OpenEverest maintainers.
Provider for MariaDB updates
At the beginning of August we introduced the Provider for MariaDB, built on top of mariadb-operator/mariadb-operator. The operator is so feature-rich that adding everything it offers to the provider will take a while — but we are making steady progress.
This month we added:
- A new topology based on Galera for high availability, along with node affinity for both Galera and standalone deployments (PR #45).
- On-demand backups and restores (PR #48).
- Scheduled backups (PR #54).
Introducing Provider for Cassandra
Our community raised a request for Cassandra support in OpenEverest. The k8ssandra-operator is well known in the industry and widely used in production, so it was an easy choice as the base for the provider.
We scaffolded it just a week ago, so it is not feature-rich yet — but it is a start, and more is on the way.
Provider for Valkey updates
The community Valkey operator is under heavy development, with new features and versions landing constantly. It is still early days, but we are keeping pace.
This week we bumped the Provider for Valkey to operator version 0.5.0 and added TLS transport encryption:
- Upgraded the underlying valkey-operator to 0.5.0.
- Added TLS transport encryption — enabled by default for all Valkey clusters.
Provider for CloudNativePG updates
The Provider for CloudNativePG, built on CloudNativePG, also moved forward this month (thanks to @adityapimpalkar):
- Restore support. The provider can now perform a full restore from a backup using CloudNativePG together with the Barman plugin.
- Integration tests migrated to Chainsaw. Entire integration suite moved from Kuttl to Chainsaw for a cleaner assertion model and more modern end-to-end testing.
- Releases. v0.2.1 (Aug 14) was a packaging release; v0.2.2 (Aug 20) fixed Helm chart dependencies for release builds and test-pipeline compatibility.
Try v2 and join the community
OpenEverest v2 is moving fast, and the best way to shape it is to get hands-on. Spin up the 2.0.0-dev.2 Developer Preview on a fresh cluster, try the new everestctl, instance presets, and point-in-time recovery, and tell us what works and what doesn’t. Have an idea for a provider or plugin? Come build it with us.
Shivansh Sinha
Chi Fujii
