[RELEASE] Scylla Operator 1.12.0

The ScyllaDB team is pleased to announce the release of Scylla Operator 1.12.0.

Scylla Operator is an open-source project that helps ScyllaDB Open Source and ScyllaDB Enterprise users run ScyllaDB on Kubernetes. The Scylla 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.

Scylla Operator 1.12.0 improves stability and brings new features. As with all of our releases, all API changes are backward compatible.

Notable changes

  • Scylla Operator now supports arm64 architecture in addition to amd64. The scylla operator image uses a manifest list to seamlessly integrate multiarch images without needing any changes. (Users still use the same tag.)
  • Scylla Operator now fully supports Alternator, an Amazon DynamoDB compatible API, within our ScyllaCluster API and provides HTTPS with automatically generated certificates to enhance security by default. The old port option has been deprecated in favor of using standard Kubernetes concepts like Services and should not be used any longer. (#1719)
  • ScyllaDB pods are now gracefully evicted and respect PDBs. (#1598)
  • ScyllaClusters now support configuring labels and annotations for most managed objects. (#1665, #1664)
  • NodeConfig can now set up storage even without extra physical disks which is helpful for dev environments or machines without extra NVMes. (#1691)
  • Graceful termination and traffic fixes. (#1707, #1738)
  • Our custom resources now support server side printers for better UX when using kubectl. (#1730)
  • Notable documentation enhancements

Supported versions

  • ScyllaDB Open Source >=5.2, ScyllaDB Enterprise >=2022.1
  • Kubernetes >=1.21
  • Container Runtime Interface API == v1
  • ScyllaDB Manager >=3.2.6

Upgrade instructions

Upgrading from v1.11.x with kubectl apply doesn’t require any extra action, just take the manifest from v1.12.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.

Getting started with Scylla Operator

  • Scylla Operator Documentation
  • Learn how to deploy Scylla on Google Kubernetes Engine (GKE) here
  • Learn how to deploy Scylla on Amazon Elastic Kubernetes Engine (EKS) here
  • Learn how to deploy Scylla on a Kubernetes Cluster here

Related Links

We’ll welcome your feedback! Feel free to open an issue or reach out on the #scylla-operator channel in Scylla User Slack.


Scylla Operator Team