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 the cass-operator to next version, we need to ensure that the label queries are correct and that k8ssandra-operator does similar label replacement (if required) to its objects.
Also, we should ensure that none of the cass-operator object queries use object names (because this is far more difficult to change and track), instead it should always be label queries to find the correct ones.
Why do we need it?
To avoid conflicts and incorrect resources from being fetched if two clusters use the same DatacenterName overrides.
Environment
K8ssandra Operator version:
Insert image tag or Git SHA here
Anything else we need to know?:
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-291
The text was updated successfully, but these errors were encountered:
What is missing?
k8ssandra/cass-operator#691
When updating the cass-operator to next version, we need to ensure that the label queries are correct and that k8ssandra-operator does similar label replacement (if required) to its objects.
Also, we should ensure that none of the cass-operator object queries use object names (because this is far more difficult to change and track), instead it should always be label queries to find the correct ones.
Why do we need it?
To avoid conflicts and incorrect resources from being fetched if two clusters use the same DatacenterName overrides.
Environment
K8ssandra Operator version:
Insert image tag or Git SHA here
Anything else we need to know?:
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-291
The text was updated successfully, but these errors were encountered: