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

Configure Reaper as StatefulSet #1275

Open
2 of 6 tasks
emerkle826 opened this issue Apr 10, 2024 · 0 comments
Open
2 of 6 tasks

Configure Reaper as StatefulSet #1275

emerkle826 opened this issue Apr 10, 2024 · 0 comments
Labels
enhancement New feature or request ready Issues in the state 'ready'

Comments

@emerkle826
Copy link
Contributor

emerkle826 commented Apr 10, 2024

Once thelastpickle/cassandra-reaper#1487 is complete, we need to be able to configure Reaper as a StatefulSet (instead of a Deployment) when Reaper uses its Memory Storage backend. When configured with the memory storage backend, Reaper will not need a Cassandra database to store its data, nor will we need an instance of Reaper deployed in every K8s cluster running a Cassandra cluster that we want to manage repairs for.

Depends upon

  1. done
    emerkle826
  2. done

Definition of Done

@emerkle826 emerkle826 added the enhancement New feature or request label Apr 10, 2024
@adejanovski adejanovski added the ready Issues in the state 'ready' label Apr 10, 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 ready Issues in the state 'ready'
Projects
Status: Ready
Development

No branches or pull requests

2 participants