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

Allow passing environment variables to Reaper #1449

Closed
a-mroz opened this issue Nov 8, 2024 · 1 comment · Fixed by #1448
Closed

Allow passing environment variables to Reaper #1449

a-mroz opened this issue Nov 8, 2024 · 1 comment · Fixed by #1448
Labels
enhancement New feature or request

Comments

@a-mroz
Copy link
Contributor

a-mroz commented Nov 8, 2024

Is your feature request related to a problem? Please describe.
I'm trying to deploy Cassandra 5 with Reaper. Unfortunately, Reaper cannot start, due to Unknown function dateof called error.

I'd like to try the workaround described here, but there seems to be no way of passing environment variables to Reaper (at least documented in the docs).

Describe the solution you'd like
Expose env for reaper, similarly to what Cassandra has.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-290

@a-mroz a-mroz added the enhancement New feature or request label Nov 8, 2024
@a-mroz
Copy link
Contributor Author

a-mroz commented Nov 12, 2024

For this particular case (REAPER_SKIP_SCHEMA_MIGRATION), I found that there's an option skipSchemaMigration defined in Reaper.spec, however it's not defined in K8ssandraCluster.spec.reaper.

@adejanovski adejanovski transferred this issue from k8ssandra/k8ssandra Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant