Split operator auxiliary processes out of ScyllaDB container and remove the need to copy the operator binary there

scylladb / scylla-operator

The Kubernetes Operator for ScyllaDB

https://operator.docs.scylladb.com/

Apache License 2.0

332 stars 162 forks source link

Split operator auxiliary processes out of ScyllaDB container and remove the need to copy the operator binary there #1943

Open tnozicka opened 4 months ago

tnozicka commented 4 months ago

We should avoid running any operator logic in ScyllaDB container, as it's bad design and hurts ScyllaDB latency.

This will also effectively remove the hack where we copy the scylla-operator binary into the ScyllaDB container which takes a lot of time (init container has low cpu allocation) and significantly slows down the node start up time.

- [ ] https://github.com/scylladb/scylla-operator/issues/620
- [ ] https://github.com/scylladb/scylla-operator/issues/1941
- [ ] https://github.com/scylladb/scylla-operator/issues/1942
- [ ] https://github.com/scylladb/scylla-operator/issues/1720
- [ ] https://github.com/scylladb/scylla-operator/issues/604

scylla-operator-bot[bot] commented 2 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 2 months ago

/remove-lifecycle stale /triage accepted