[RELEASE] ScyllaDB Operator 1.8.0

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

ScyllaDB Operator is an open-source project that helps ScyllaDB Open Source and ScyllaDB Enterprise users run ScyllaDB on Kubernetes. ScyllaDB Operator manages ScyllaDB clusters deployed to Kubernetes and automates tasks related to operating a ScyllaDB cluster, like installation, scale out and downscale, as well as rolling upgrades.

ScyllaDB Operator 1.8.0 improves stability and brings a few features. As with all of our releases, any API changes are backwards compatible.

Notable changes

  • Experimental - Ingress objects are now reconciled for each ScyllaCluster node (#993)
  • Experimental - Managed TLS Certificates allowing users to enable client-node encryption (#1021)
  • ScyllaCluster status has been extended with Conditions improving observability (#1070)
  • PodDisruptionBudgets reconciled by the Operator are using v1 API version which fixes support for newer Kubernetes version, where v1beta1 version was removed. (#1005)
  • Custom annotations added by users on managed ServiceAccount object are not removed on reconciliation (#933)
  • Fixed the decommission procedure for drained node (#967)
  • Idle connections to ScyllaDB API are closed after Operator no longer needs them, fixing OOM issues happening months after ScyllaCluster creation (#1017)
  • Fixed repository paths to allow vendoring of our source code (#1098)

For more changes and details check out the GitHub release notes.

Supported versions

  • ScyllaDB ≥5.0, ScyllaDB Enterprise ≥2021.1
  • Kubernetes ≥1.21
  • Scylla manager ≥2.6
  • Scylla monitoring ≥4.0

Upgrade instructions

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

  • 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 (including MiniKube example)

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.

Regards,

ScyllaDB Operator Team