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

[Multi-DC] Configuration Synchronization Across Multiple Datacenters #2255

Open
Tracked by #2230
ylebi opened this issue Dec 12, 2024 · 0 comments
Open
Tracked by #2230

[Multi-DC] Configuration Synchronization Across Multiple Datacenters #2255

ylebi opened this issue Dec 12, 2024 · 0 comments
Assignees
@zimnx
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.16.0

Comments

@ylebi
Copy link
Collaborator

ylebi commented Dec 12, 2024 •
edited
Loading

In order to reduce manual intervention and the risk of misconfigurations we need to improve user experience by ensuring ConfigMap is synchronized across multiple datacenters.
@ylebi ylebi mentioned this issue Dec 12, 2024
Open
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Dec 12, 2024
@ylebi ylebi changed the title Configuration isn't synchronized across multiple datacenters Configuration Synchronization Across Multiple Datacenters Dec 12, 2024
@ylebi ylebi added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Dec 12, 2024
@zimnx zimnx self-assigned this Dec 12, 2024
@ylebi ylebi changed the title Configuration Synchronization Across Multiple Datacenters [Multi-DC] Configuration Synchronization Across Multiple Datacenters Dec 15, 2024
@zimnx zimnx added this to the v1.16.0 milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimnx zimnx

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.16.0
Development

No branches or pull requests
2 participants
@zimnx @ylebi