The ScyllaDB team is pleased to announce the release of Scylla Operator 1.11.3 
.
Scylla Operator 1.11.3 brings a bug fix.
As with all of our releases, all API changes are backward compatible.
Notable changes
- We have recently found out that if we set up CQL-SSL in a ScyllaDB cluster, Scylla Manager would configure a TLS client by default when establishing a CQL session with the cluster, even if it wasn’t provided with any certificates. Such behaviour would result in Scylla Manager being unable to carry out a restore procedure. While this could have been worked around by disabling the
AutomaticTLSCertificatesfeature gate before, the issue has since been fixed in Scylla Manager 3.2.6. To fix the issue in Scylla Operator, we now explicitly disable CQL over TLS in cluster integration with Scylla Manager (#1817). Note, however, that for the changes to take effect, you will need to update your Scylla Manager deployment to 3.2.6.
For more changes and details check out the GitHub release notes.
Upgrade instructions
When using kubectl apply, upgrading from v1.10.x or v1.11.x doesn’t require any additional actions, just take the manifest from v1.11.3 tag and substitute for the image. Since helm isn’t capable of handling CRD updates, using helm requires a mandatory manual step for every release.
For details, see our upgrade documentation.
Best regards,
Scylla Operator Team.