-
Notifications
You must be signed in to change notification settings - Fork 66
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
K8SSAND-1636 ⁃ Allow the Cassandra DC name to be different than the CassandraDatacenter name #362
Closed
1 task done
Labels
Comments
sync-by-unito
bot
changed the title
Allow the Cassandra DC name to be different than the CassandraDatacenter name
K8SSAND-1636 ⁃ Allow the Cassandra DC name to be different than the CassandraDatacenter name
Jul 7, 2022
adejanovski
added
zh:Assess/Investigate
and removed
zh:Review
zh:Assess/Investigate
labels
Aug 30, 2022
adejanovski
added
in-progress
Issues in the state 'in-progress'
and removed
ready
Issues in the state 'ready'
labels
Jan 5, 2023
This was referenced Jan 9, 2023
adejanovski
added
ready-for-review
Issues in the state 'ready-for-review'
and removed
in-progress
Issues in the state 'in-progress'
labels
Jan 16, 2023
adejanovski
added
review
Issues in the state 'review'
and removed
ready-for-review
Issues in the state 'ready-for-review'
labels
Jan 17, 2023
adejanovski
added
review
Issues in the state 'review'
and removed
ready-for-review
Issues in the state 'ready-for-review'
labels
Jan 17, 2023
adejanovski
added
done
Issues in the state 'done'
and removed
review
Issues in the state 'review'
labels
Jan 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on
What is missing?
The DC name as stored in Cassandra is always configured to be the same as the CassandraDatacenter name. We need to be able to specify a different name for the DC as stored in Cassandra.
Why do we need it?
This is needed in k8ssandra-operator to avoid naming collisions. See k8ssandra/k8ssandra-operator#615.
This can be supported pretty easily with a small change in the
GetConfigAsJSON
method (see here) by allowing properties under thedatacenter-info
key to be overridden. I will try to include a unit test for good measure.Environment
Cass Operator version:
**Anything else we need to know?**:v1.11.0
Update
After discussing this offline, we want to apply the same strategy as what's been done with cluster name overrides in k8ssandra-operator:
DcName
field which will allow name overrides that aren't compliant with Kubernetes object namesIn a nutshell, a new method will be created in the cassdc api looking as follows:
Wherever the
cassdc.Name
was previously use, we'll have to usecassdc.SanitizedName()
instead, unless we want to refer directly to the cassdc object.┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1636
┆priority: Medium
The text was updated successfully, but these errors were encountered: