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

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

Open
3 of 6 tasks
ylebi opened this issue Jan 13, 2025 · 0 comments
Labels
kind/epic Categorizes issue as an epic. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ylebi
Copy link
Collaborator

ylebi commented Jan 13, 2025

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.

Ref: #1943

Tasks

Preview Give feedback
  1. kind/epic priority/important-longterm
    tnozicka
  2. kind/feature priority/important-soon triage/accepted
    tnozicka
  3. kind/feature priority/important-soon triage/accepted
  4. kind/cleanup priority/important-soon triage/accepted
    zimnx
  5. kind/feature lifecycle/from-migration priority/important-soon triage/accepted
  6. kind/feature priority/important-longterm
@ylebi ylebi added kind/epic Categorizes issue as an epic. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 13, 2025
@mflendrich mflendrich added the lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Categorizes issue as an epic. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants