-
Notifications
You must be signed in to change notification settings - Fork 181
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Node setup fails on filesystem creation in Categorizes issue or PR as related to a bug.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
v1.32.3-gke.1170000
kind/bug
#2579
opened Apr 9, 2025 by
rzetelskik
Changed the source of the ScyllaDBVersion parameter value in scyllacluster_replace test
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
kind/bug
Categorizes issue or PR as related to a bug.
lgtm
Indicates that a PR is ready to be merged.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
#2578
opened Apr 9, 2025 by
grzywin
Loading…
Local CSI Driver installation is missing from Helm installation guide
kind/bug
Categorizes issue or PR as related to a bug.
kind/documentation
Categorizes issue or PR as related to documentation.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
#2567
opened Apr 1, 2025 by
rzetelskik
Automated backups are broken with ScyllaDB OS >=6.0 and Enterprise >=2024.2 when ScyllaClusters are set up with AuthN
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2548
opened Mar 12, 2025 by
rzetelskik
Operator can't replace a node when different node Service has wrong state
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2521
opened Feb 27, 2025 by
zimnx
[Multi-DC] Reconcile remote datacenters independently
kind/bug
Categorizes issue or PR as related to a bug.
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.
Prevent or handle replacing unbootstrapped nodes
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.
#2447
opened Feb 4, 2025 by
mflendrich
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
Limit aggregated conditions to fit into API limits
good-first-issue
Issue that is good as an onboarding task for newcomers
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/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2443
opened Feb 4, 2025 by
mflendrich
Scaling cluster down and up before it's finished gets the cluster stuck
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.
#2436
opened Feb 4, 2025 by
mflendrich
Apply flow can inherit data from previous incarnation of the object
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.
#2412
opened Feb 4, 2025 by
mflendrich
Retry NodeConfig mounts
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.
#2406
opened Feb 4, 2025 by
mflendrich
Disable JMX debug endpoint
area/security
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.
#2386
opened Feb 4, 2025 by
mflendrich
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
Substitute correct manifests version in a particular docs version
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.
#2364
opened Feb 4, 2025 by
mflendrich
API reference generation produces invalid RST for multiline scalars
good-first-issue
Issue that is good as an onboarding task for newcomers
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2334
opened Jan 15, 2025 by
rzetelskik
node tuning: failed to list *v1.Job: Unauthorized
kind/bug
Categorizes issue or PR as related to a bug.
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.
#2287
opened Dec 19, 2024 by
adnankobir
[Multi-DC] Cleanup shouldn't be run on every scaling event
kind/bug
Categorizes issue or PR as related to a bug.
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.
#2264
opened Dec 12, 2024 by
ylebi
[Multi-DC] Clients can't connect to multi datacenter cluster using TLS
kind/bug
Categorizes issue or PR as related to a bug.
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.
#2263
opened Dec 12, 2024 by
ylebi
Alternator's user managed serving certificate is not supported
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2248
opened Dec 9, 2024 by
rzetelskik
ScyllaClusters connected into a multi-datacenter cluster with Categorizes issue or PR as related to a bug.
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.
externalSeeds
are registered as separate clusters with Scylla Manager
kind/bug
#2119
opened Sep 10, 2024 by
rzetelskik
AggregateStatusConditions
can produce invalid Condition
kind/bug
#2102
opened Aug 29, 2024 by
rzetelskik
Manager offline status in Grafana when following instructions from 'basic-setup'
kind/bug
Categorizes issue or PR as related to a bug.
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.
#2079
opened Aug 16, 2024 by
grzywin
Prometheus metrics relabel is not up to date
kind/bug
Categorizes issue or PR as related to a bug.
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.
#1672
opened Jan 4, 2024 by
amnonh
Init container gets OOM killed on new cluster POD startup
kind/bug
Categorizes issue or PR as related to a bug.
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.
#1566
opened Nov 14, 2023 by
andrey-dubnik
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.