Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

nagasree963_193876 avatar image
nagasree963_193876 asked nagasree963_193876 commented

Can we upgrade cassandra-operator 1.1.0 to 1.5.1?

I have few questions on cass-operator upgrade. Please anyone clarify on the below ones:

1) Can we directly upgrade the operator version from 1.1.0 to 1.5.1

2) I donot see any much feature difference between the versions. I can still see, it is not supporting backup and restore one

3) As we are using cass-operator, How can we shift from existing one to k8ssandra

cass-operatork8ssandra
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered nagasree963_193876 commented

To upgrade the operator, you will need to apply the manifest YAML for cass-operator 1.5.1. For details, see Upgrade Cassandra Operator and related resources in Kubernetes.

There isn't a documented migration path to k8ssandra for existing clusters already using the cass-operator. I've previously logged a request to have this process documented (issue #377). Cheers!

3 comments Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

What I understood from the link (Upgrade Cassandra Operator and related resources in Kubernetes. ), I have to first upgrade to 1.4.0 and then to 1.5.1. Is there any issue if I upgrade directly from 1.1.0 to 1.5.1.

0 Likes 0 ·

I have deployed cass-operator-1.1.0 to 1.4.1 as suggested in that documentation. Later, I have updated to 1.5.0 . It was updated successfully. But one of my cassandra datacenter pods goes to pending state. Before that all pods are in running state.


kubectl -n cass-operator get po

NAME READY STATUS RESTARTS AGE

cass-operator-cb985c584-wh2pp 1/1 Running 0 11m

cluster1-dc1-default-sts-0 2/2 Running 0 129m

cluster1-dc1-default-sts-1 2/2 Running 0 131m

cluster1-dc1-default-sts-2 0/2 Pending 0 11m

0 Likes 0 ·

Can anyone please help me on this issue. I was trying to update cassandra operator from 1.1.0 to 1.5.1. Whenever I am applying operator file. cassandra pods are going to pending state without any change in cr file. Is there any need to change in cr if want upgrade the opertaor to 1.5.1

0 Likes 0 ·