You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to allow deploying a single instance of Reaper which will repair all K8ssandraClusters managed by a single control plane.
This requires to create a new deployment mode in Reaper (aside from PER_DC and SINGLE), which we can name "CONTROL_PLANE".
A Reaper custom resource would need to be created separately prior to the K8ssandraCluster objects creation, with this mode.
Any K8ssandraCluster object without Reaper settings would be registered by the operator into the control plane Reaper and repairs would be managed by it.
We would disallow enabling Reaper in clusters if the control plane instance exists to keep things simple in the first iteration.
This means either you have one centralized Reaper managing all clusters or you have individual Reaper instances per cluster.
The content you are editing has changed. Please copy your edits and refresh the page.
We want to allow deploying a single instance of Reaper which will repair all K8ssandraClusters managed by a single control plane.
This requires to create a new deployment mode in Reaper (aside from PER_DC and SINGLE), which we can name "CONTROL_PLANE".
A Reaper custom resource would need to be created separately prior to the K8ssandraCluster objects creation, with this mode.
Any K8ssandraCluster object without Reaper settings would be registered by the operator into the control plane Reaper and repairs would be managed by it.
We would disallow enabling Reaper in clusters if the control plane instance exists to keep things simple in the first iteration.
This means either you have one centralized Reaper managing all clusters or you have individual Reaper instances per cluster.
Definition of Done
The text was updated successfully, but these errors were encountered: