Limit ScyllaDB restarts on updates

[tnozicka]

At this point, every scylla-operator release causes a rolling restart on scylla to update the sidecar that is run alongside scylla, even when none of the sidecar logic has changed.

We should split the sidecar logic into it's own repo and image that would provide probes and starter logic.

Note that at this point, there are [parts of the operator logic within the sidecar that shouldn't be there[(#604) and we need to remove them first.

Requires

• Move scylla config creation into the operator #604

Tasks

Tasks

Preview Give feedback

1. Move scylladb config creation from sidecar to the operator #1714
   kind/cleanup priority/important-soon +2
2. Move ScyllaDB rack properties generation out of the sidecar #1720
   kind/cleanup priority/important-soon triage/accepted +3
   

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale
/triage accepted