Skip to content

Instead of using envVariables, build the entire cassandra-reaper.yaml#1659

Draft
burmanm wants to merge 3 commits intok8ssandra:mainfrom
burmanm:reaper_config_file_moun
Draft

Instead of using envVariables, build the entire cassandra-reaper.yaml#1659
burmanm wants to merge 3 commits intok8ssandra:mainfrom
burmanm:reaper_config_file_moun

Conversation

@burmanm
Copy link
Copy Markdown
Contributor

@burmanm burmanm commented Dec 23, 2025

What this PR does:
For Reaper v4 and newer, build the entire cassandra-reaper.yaml in the k8ssandra-operator instead of using envVars. This is prerequisite for another PR that adds optional feature modifications such as TLS for the endpoints (which is a non-supported process in the env variables)

TODO: Modify the e2e test to verify the resulting cassandra-reaper.yaml in the container

Which issue(s) this PR fixes:
Fixes #1658

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CHANGELOG.md updated (not required for documentation PRs)
  • CLA Signed: DataStax CLA

… in the k8ssandra-operator. This only applies to Reaper v4 and newer.
…n the container to allow schema-migration to work
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Modify Reaper configuration to write the YAML file instead of only envVars

1 participant