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

Enrich configs #514

Closed
Tracked by #512
burmanm opened this issue Mar 22, 2023 · 0 comments · Fixed by #540
Closed
Tracked by #512

Enrich configs #514

burmanm opened this issue Mar 22, 2023 · 0 comments · Fixed by #540
Labels
done Issues in the state 'done' enhancement New feature or request

Comments

@burmanm
Copy link
Contributor

burmanm commented Mar 22, 2023

What is missing?

Current cass-config-builder will enrich the following keys of the config that's given from cass-operator:

  • cassandra-yaml
  • cassandra-env-sh
  • dse
  • datastax-env-sh
  • cassandra-rack-properties

In the cassandra-yaml, we need to take care of several properties that the user should not override and we should always. These include seed_provider, cluster_name as well as:

(def node-private-props #{:listen_address
                          :broadcast_address
                          :native_transport_address
                          :native_transport_broadcast_address
                          :rpc_address
                          :broadcast_rpc_address
                          :seed_provider
                          :initial_token
                          :auto_bootstrap})

And from the definitions, we'll need listen_address and such. Some of these are defined in the mcctl already, some have different settings depending on the version we'll support.

Why is this needed?

Otherwise the configuration that's applied might not work correctly in our environment.

@burmanm burmanm added the enhancement New feature or request label Mar 22, 2023
@burmanm burmanm moved this to Assess/Investigate in K8ssandra Apr 27, 2023
@adejanovski adejanovski added the assess Issues in the state 'assess' label Jul 24, 2023
@github-project-automation github-project-automation bot moved this from Assess/Investigate to Done in K8ssandra Aug 16, 2023
@adejanovski adejanovski added done Issues in the state 'done' and removed assess Issues in the state 'assess' labels Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done Issues in the state 'done' enhancement New feature or request
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants