The ScyllaDB team is pleased to announce the release of ScyllaDB Operator 1.17.0.
ScyllaDB Operator is an open-source project that helps users run ScyllaDB on Kubernetes. The ScyllaDB Operator manages ScyllaDB clusters deployed to Kubernetes and automates tasks related to operating a ScyllaDB cluster, like installation, vertical and horizontal scaling, as well as rolling upgrades.
As with each minor version, ScyllaDB Operator 1.17 adds new features and improves stability. What makes this release special is the technical preview of managed multi-datacenter ScyllaDB clusters.
Managed Multi-DC
ScyllaDB Operator 1.17 introduces a new deployment pattern: a ScyllaDB cluster spanning across multiple datacenters (regions) running in distinct Kubernetes clusters:
Image credit: Maciej Zimnoch @zimnx
This functionality allows you to run a “Multi-DC control plane” in one place, and specify your ScyllaDB installation spanning across many (e.g. 3) datacenters (for example, cloud regions), each running its own Kubernetes cluster. ScyllaDB Operator will then manage a consistent, highly-available deployment, utilizing ScyllaDB’s multi-datacenter replication technology.
Multi-DC installations are governed by the newly introduced ScyllaDBCluster CRD. Try it out by following the AWS EKS and Google Cloud GKE quickstart guides. See documentation for more.
Managed Multi-DC in ScyllaDB Operator 1.17 comes as a technical preview, enabling configuration and core lifecycle management of the Multi-DC ScyllaDB cluster. Monitoring and backup/repair (using ScyllaDB Manager) are available, but require manual setup (automation to be incrementally included in subsequent minor releases - please stay tuned to future announcements). Please refer to the Multi-DC operator enhancements tracking issue on GitHub.
Other notable changes
This release brings support for new ScyllaDB 2025.1 and ScyllaDB Manager 3.5.0, and includes a major Prometheus version upgrade (v2.54.1 → v3.1.0) as well as updated Grafana (11.3.0 → 11.4.3) and our newest ScyllaDB monitoring dashboards (#2623).
The default storage capacity in the Helm chart and the deploy manifests has been adjusted from 10 GB to 120 GB which is more useful for typical workloads (#2565).
Also, ScyllaDB Operator 1.17 fixes an important bug that could lead to storage exhaustion upon upgrade on the first node of the rack due to leftover keyspace snapshots. The fix is available in 1.16.2 as well. (#2528)
For more changes and details, check out the GitHub release notes.
Upgrade instructions
Upgrading from v1.16.x with kubectl apply doesn’t require any extra action, just take the manifest from v1.17.0 tag and substitute the released image. Using helm requires a mandatory manual step for every release because helm can’t handle CRDs updates. For details, see our upgrade documentation.
Supported versions
- ScyllaDB >=2023.1 && <=2025.1,
- Kubernetes >=1.25,
- Container Runtime Interface API == v1,
- ScyllaDB Manager >=3.3.3 && <=3.5.
Getting started with ScyllaDB Operator
- ScyllaDB Operator Documentation
- Learn how to deploy ScyllaDB on Google Kubernetes Engine (GKE) here
- Learn how to deploy ScyllaDB on Amazon Elastic Kubernetes Engine (EKS) here
- Learn how to deploy ScyllaDB on a Kubernetes Cluster here
Related Links
- ScyllaDB Operator source (on GitHub)
- ScyllaDB Operator image on DockerHub
- ScyllaDB Operator Helm Chart repository
- ScyllaDB Operator documentation
- ScyllaDB Operator for Kubernetes lesson in ScyllaDB University
- Report a problem
We’ll welcome your feedback! Feel free to open an issue or reach out on the #scylla-operator channel in ScyllaDB User Slack.
Regards,
The ScyllaDB Operator Team