Skip to content

Issues: scylladb/scylla-operator

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

Clear current search query, filters, and sorts
3 Open 0 Closed
3 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

NodeConfig tuning: no scylla container found in pod area/node-config kind/bug Categorizes issue or PR as related to a bug. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#2445 opened Feb 4, 2025 by mflendrich
@zimnx
Overlapping NodeConfigs don't track their resources correctly and fight with each other area/node-config kind/bug Categorizes issue or PR as related to a bug. 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.
#2371 opened Feb 4, 2025 by mflendrich
Reduce XFS metadata overhead area/node-config good-first-issue Issue that is good as an onboarding task for newcomers kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. 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.
#2353 opened Jan 27, 2025 by zimnx
1
3
ProTip! Exclude everything labeled bug with -label:bug.