Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update of Pod labels fails when going from 1.22.4 to 1.23.0 #765

Open
burmanm opened this issue Feb 27, 2025 · 0 comments
Open

Update of Pod labels fails when going from 1.22.4 to 1.23.0 #765

burmanm opened this issue Feb 27, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@burmanm
Copy link
Contributor

burmanm commented Feb 27, 2025

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

@burmanm burmanm added the bug Something isn't working label Feb 27, 2025
@burmanm burmanm self-assigned this Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant