# \[RELEASE\] ScyllaDB Operator 1.19.2

**URL:** <https://forum.scylladb.com/t/release-scylladb-operator-1-19-2/5314>\
**Category:** Release Notes\
**Tags:** release, operator, operator-release\
**Created:** [March 20, 2026, 9:35am UTC](https://forum.scylladb.com/t/release-scylladb-operator-1-19-2/5314 "2026-03-20T09:35:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kacper\_Rzetelski](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/kacper_rzetelski/32/695_2.png) [@Kacper\_Rzetelski](https://forum.scylladb.com/u/Kacper_Rzetelski)\
**Post date:** [March 20, 2026, 9:35am UTC](https://forum.scylladb.com/t/release-scylladb-operator-1-19-2/5314/1 "2026-03-20T09:35:38Z")

</div>

We are pleased to announce the release of ScyllaDB Operator 1.19.2

Release highlights:

- 🐛 `Pod` annotation “[internal.scylla.scylladb.com/scylladb-node-status-report](http://internal.scylla.scylladb.com/scylladb-node-status-report)” and `ScyllaDBDatacenterNodeStatusReport` objects now use stable ordering of entries, preventing random reordering and frequent updates resulting in unstable `ScyllaCluster`/`ScyllaDBDatacenter` status conditions.
- 🐛 Fixed `ScyllaCluster` status conditions not properly surfacing errors from child resources (e.g., `ScyllaDBManagerTask` apply failures) and misreporting observed generation after certain spec changes (e.g., `.spec.sysctls`), which could make the `Progressing`, `Degraded`, and `Available` conditions unreliable.
- ⚠ Admission webhook now warns when `ScyllaCluster` backup or repair task names don’t comply with RFC 1123 (e.g., containing underscores `_`) - **these will become errors in the next minor release (1.21)**.

For the full list of changes, please refer to the [changelog](https://github.com/scylladb/scylla-operator/blob/master/CHANGELOG.md#1192).