Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

First-class support (or an officially supported recipe) for multi-Kubernetes / multi-region DR

Aperta
  • Qualcosa non va?
#2,105 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
documentation, infrastructure

Direzione di ricerca

This is a design question, not a code change yet. Start with the recovery-architecture doc linked in the issue and the CHI settings it mentions, zookeeper.nodes and remote_servers, to see what the operator already supports across clusters. A first useful step is a scoping discussion with maintainers on whether a docs and test checklist for two-CHI primary/warm-standby is accepted. Done means an agreed scope, not an implementation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

We run ClickHouse via clickhouse-operator (currently looking at 0.27.x) and need a clear story for disaster recovery across Kubernetes clusters, often in different regions: primary site + warm standby (or equivalent), with a tested failover path.

Today the operator is excellent inside a single Kubernetes cluster, but multi-site DR still looks like DIY. We’d like this to become a first-class, documented, and tested capability — or at least an explicitly supported topology with a maintained guide tied to operator releases.

What we need

Something teams can rely on in production, for example:

  1. Documented supported topology for primary / warm-standby (or another Altinity-recommended shape) across two Kubernetes clusters / regions, including Keeper placement (voting members vs observers), naming/{replica} rules, and failover / failback steps.
  2. Operator-level help where it makes sense — even if a full “Federated CHI” is a bigger project. Examples: clearer cross-site guidance in-tree, validation/warnings, helpers for remote_servers / macros, or a thin multi-cluster controller later.
  3. Soak / failover testing so this isn’t only a blog/webinar recipe.

We’re fine doing networking ourselves (peering, DNS, service exposure). The gap is knowing what’s supported vs best-effort, and not inventing a one-off design that breaks on the next operator upgrade.

What we already understand (not asking for this)
  • CHI is namespaced and the operator reconciles inside one Kubernetes cluster — that matches what we’ve seen in the CRD and in your materials.
  • Multiple entries in spec.configuration.clusters[] in one CHI are a same-cluster layout, not multi-region DR.
  • A real CHK is one Raft ensemble; we won’t treat extra CHK clusters[] examples as multi-site Keeper HA.
  • Cross-region setups are possible today with two operators/CHIs, shared Keeper via zookeeper.nodes, and a lot of network/DNS work (as in your blog and #1380).

Your DR webinar also called this out directly:

The operator operates within a single Kubernetes cluster, so multi-cluster deployments require something sitting outside the operator itself. […] eBay […] implemented a “Federated ClickHouseInstallation” […] We did not build it yet because the multi-region DR scenario is rare enough that it has not risen to the top of the priority list. But we are totally open to collaborating on it.

We’re essentially asking to raise the priority of that gap (docs + tests first is already valuable; federation later if it makes sense).

References
Ask
  1. Is multi-Kubernetes / multi-region DR on the operator roadmap?
  2. Short of a federated controller, would you accept / help maintain an official in-repo guide + test checklist for the primary/warm-standby pattern with two CHIs?
Lingua principale
Go
Stelle
2.6k
Fork
579
Merge medio
21h 2m
PR unite (30g)
4

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Altinity/clickhouse-operator

Tutte le issue di Altinity/clickhouse-operator

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.