Split operator sidecar out of ScyllaDB container

tnozicka commented 6 months ago

Operator sidecar that queries ScyllaDB and reflects its state into the API, among other things, should run in a separate container. It can still reach ScyllaDB through localhost from the same Pod.

See https://github.com/scylladb/scylla-operator/issues/1940 for more context.

scylla-operator-bot[bot] commented 4 months ago

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 commented 4 months ago

/remove-lifecycle stale /triage accepted

scylladb / scylla-operator

Split operator sidecar out of ScyllaDB container #1942