# Multi-k8s cluster, single datacenter sanity check

**URL:** <https://discuss.hashicorp.com/t/multi-k8s-cluster-single-datacenter-sanity-check/48575>\
**Category:** Consul\
**Created:** [January 5, 2023, 12:13am UTC](https://discuss.hashicorp.com/t/multi-k8s-cluster-single-datacenter-sanity-check/48575 "2023-01-05T00:13:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mschultz-aofl](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/mschultz-aofl/32/32915_2.png) [@mschultz-aofl](https://discuss.hashicorp.com/u/mschultz-aofl)\
**Post date:** [January 5, 2023, 12:13am UTC](https://discuss.hashicorp.com/t/multi-k8s-cluster-single-datacenter-sanity-check/48575/1 "2023-01-05T00:13:30Z")

</div>

Hey, I haven’t seen this anywhere in the docs, but for my usecase (multiple K8S clusters, completely flat hierarchy) I was wondering if it’s possible/recommended to run consul server on multiple clusters, so if one goes down, another leader will be elected in a different cluster? The goal here is to avoid federation, which requires a primary DC and thus a single point of failure.

So I would have  
Cluster A, Consul server[0-3], UI exposed via LB  
Cluster B, Consul server[4-6], UI exposed via LB

From what I can tell, this might not be possible? It’s not described anywhere, but it would be immensely helpful in a DR scenario where an entire cluster goes down.