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.

Sign up for GitHub

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

Jump to bottom

Move ScyllaDB rack properties generation out of the sidecar #2328

Open
Tracked by #2326
ylebi opened this issue Jan 13, 2025 · 0 comments
Open
Tracked by #2326

Move ScyllaDB rack properties generation out of the sidecar #2328

ylebi opened this issue Jan 13, 2025 · 0 comments
Assignees
@zimnx
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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 move sidecar logic that generates rack properties file out of the sidecar so it's in the correct place (operator) and we can remove the need for the sidecar eventually.
@ylebi ylebi added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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
@ylebi ylebi mentioned this issue Jan 13, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimnx zimnx

Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zimnx @ylebi