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
6 Open 0 Closed
6 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

ScyllaDBMonitoring: support an external Prometheus instance area/platform/openshift kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
#2490 opened Feb 20, 2025 by mflendrich
3 tasks
5
Failing test - OpenShift: RemoteKubernetesCluster finalizer [It] should block deletion when there are ScyllaDBClusters referencing the object area/platform/openshift kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. 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.
#2489 opened Feb 20, 2025 by mflendrich
@mflendrich
OpenShift M4: Published into certified-operators area/platform/openshift kind/epic Categorizes issue as an epic. 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.
#2347 opened Jan 20, 2025 by mflendrich
4 tasks
OpenShift M3: Published into OperatorHub area/platform/openshift kind/epic Categorizes issue as an epic. 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.
#2346 opened Jan 20, 2025 by mflendrich
2 tasks
OpenShift M2: Installable with OLM area/platform/openshift 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.
#2345 opened Jan 20, 2025 by mflendrich
3 tasks
OpenShift M1: Installable and Tested area/platform/openshift 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.
#424 opened Feb 23, 2021 by ezbz
2 tasks
@mflendrich
10
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.