You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating a cluster with datacenterNameOverride in use, the v1.23.0 does not see all the pods it should update to the latest labels and instead causes the StatefulSet to go out of sync (and operator not seeing which pods it should start).
As a workaround, one can modify the pod labels to match the updated StatefulSet definition (namely, the cassandra.datastax.com/datacenter).
What did you expect to happen?
No response
How can we reproduce it (as minimally and precisely as possible)?
Make cluster with v1.22.4 using datacenterName (which is different from dc.Meta.Name) and then update that to v1.23.0
cass-operator version
1.23
Kubernetes version
1.32
Method of installation
No response
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-95
The text was updated successfully, but these errors were encountered:
What happened?
When updating a cluster with datacenterNameOverride in use, the v1.23.0 does not see all the pods it should update to the latest labels and instead causes the StatefulSet to go out of sync (and operator not seeing which pods it should start).
As a workaround, one can modify the pod labels to match the updated StatefulSet definition (namely, the cassandra.datastax.com/datacenter).
What did you expect to happen?
No response
How can we reproduce it (as minimally and precisely as possible)?
Make cluster with v1.22.4 using datacenterName (which is different from dc.Meta.Name) and then update that to v1.23.0
cass-operator version
1.23
Kubernetes version
1.32
Method of installation
No response
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-95
The text was updated successfully, but these errors were encountered: