You are not reading the latest stable version of this documentation. If you want up-to-date information, please have a look at v1.7.
This pages describes Scylla Operator upgrade procedures.
Note: There’s an experimental migration procedure available here.
v0.3.0 used a very common name as a CRD kind (
v1.0.0 this issue was solved by using less common
kind which is easier to disambiguate. (
This change is backward incompatible, so Scylla cluster must be turned off and recreated from scratch.
In case you need to preserve your data, refer to backup and restore guide.
Get list of existing Scylla clusters
kubectl -n scylla get cluster.scylla.scylladb.com NAME AGE simple-cluster 30m
Delete each one of them
kubectl -n scylla delete cluster.scylla.scylladb.com simple-cluster
Make sure you’re on
git checkout v0.3.0
Delete existing CRD and Operator
kubectl delete -f examples/generic/operator.yaml
git checkout v1.0.0
Install new CRD and Scylla Operator
kubectl apply -f examples/common/operator.yaml
Migrate your existing Scylla Cluster definition. Change
apiVersion: scylla.scylladb.com/v1alpha1 kind: Cluster
apiVersion: scylla.scylladb.com/v1 kind: ScyllaCluster
Once your cluster definition is ready, use
kubectl apply to install fresh Scylla cluster.