# \[RELEASE\] Scylla Operator 1.10.0

**URL:** <https://forum.scylladb.com/t/release-scylla-operator-1-10-0/810>\
**Category:** Release Notes\
**Tags:** release, operator, operator-release, kubernetes\
**Created:** [August 28, 2023, 8:15am UTC](https://forum.scylladb.com/t/release-scylla-operator-1-10-0/810 "2023-08-28T08:15:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![zimnx](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/zimnx/32/150_2.png) [@zimnx](https://forum.scylladb.com/u/zimnx)\
**Post date:** [August 28, 2023, 8:15am UTC](https://forum.scylladb.com/t/release-scylla-operator-1-10-0/810/1 "2023-08-28T08:15:44Z")

</div>

The ScyllaDB team is pleased to announce the release of **Scylla Operator 1.10.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.10.0 improves stability and brings a few features. As with all of our releases, any API changes are backward compatible.

# Notable changes

- Scylla Operator will automatically run [cleanup](https://enterprise.docs.scylladb.com/stable/operating-scylla/nodetool-commands/cleanup.html) procedure after ScyllaCluster scaling - it helps to avoid the accumulation of unnecessary data on the node disks ([#1294](https://github.com/scylladb/scylla-operator/pull/1294)).
- Nodes are going to be replaced using a new procedure identifying nodes using their stable identifier - [Host ID](https://github.com/scylladb/scylladb/pull/12316). New procedure will be executed only for ScyllaClusters using ScyllaDB OS \>=5.2.0 and ScyllaDB Enterprise \>=2023.1.0, older versions are going to use existing procedure ([#1312](https://github.com/scylladb/scylla-operator/pull/1312)).
- Readiness probes identify nodes using their stable identifier Host ID instead of IPv4 address - it helps with ephemeral IP deployments, and IPv6 deployments where invalid IP address was used for status comparison ([#1297](https://github.com/scylladb/scylla-operator/pull/1297)).

For more changes and details check out the [GitHub release notes](https://github.com/scylladb/scylla-operator/releases/tag/v1.10.0).

# Supported versions

- ScyllaDB Open Source \>=5.0, ScyllaDB Enterprise \>=2021.1
- Kubernetes \>=1.21
- Container Runtime Interface API == v1
- ScyllaDB Manager \>=2.6
- ScyllaDB Monitoring \>=4.0

# Upgrade instructions

Upgrading from v1.9.x with `kubectl apply` doesn’t require any extra action, just take the manifest from v1.10.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](https://operator.docs.scylladb.com/stable/upgrade.html).

## Getting started with Scylla Operator

- [Scylla Operator Documentation](https://operator.docs.scylladb.com/)
- Learn how to deploy Scylla on Google Kubernetes Engine (GKE) [here](https://operator.docs.scylladb.com/stable/gke.html)
- Learn how to deploy Scylla on Amazon Elastic Kubernetes Engine (EKS) [here](https://operator.docs.scylladb.com/stable/eks.html)
- Learn how to deploy Scylla on a Kubernetes Cluster [here](https://operator.docs.scylladb.com/stable/generic.html) (including MiniKube example)

## Related Links

- Scylla Operator [source](https://github.com/scylladb/scylla-operator) (on GitHub)
- Scylla Operator [image on DockerHub](https://hub.docker.com/r/scylladb/scylla-operator)
- Scylla Operator [Helm Chart repository](https://storage.googleapis.com/scylla-operator-charts/stable/index.yaml)
- [Scylla Operator documentation](https://operator.docs.scylladb.com/stable/)
- [Scylla Operator for Kubernetes lesson](https://university.scylladb.com/courses/scylla-operations/lessons/kubernetes-operator/) in Scylla University
- [Report a problem](https://github.com/scylladb/scylla-operator/issues)

We’ll welcome your feedback! Feel free to open an [issue](https://github.com/scylladb/scylla-operator/issues) or reach out on the #scylla-operator channel in [Scylla User Slack](http://slack.scylladb.com/).

Regards,

Scylla Operator Team