# Consul DCs federation **URL:** \ **Category:** Consul\ **Tags:** k8s\ **Created:** [November 7, 2020, 3:18am UTC](https://discuss.hashicorp.com/t/consul-dcs-federation/17318 "2020-11-07T03:18:29Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![vsirimalla](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/vsirimalla/32/3743_2.png) [@vsirimalla](https://discuss.hashicorp.com/u/vsirimalla)\ **Post date:** [November 7, 2020, 3:18am UTC](https://discuss.hashicorp.com/t/consul-dcs-federation/17318/1 "2020-11-07T03:18:29Z")
we have two consul datacenters. Both of them are on-prem datacenters, one of them is on VMs and other is going to be in kubernetes. However kubernetes cluster is in a DMZ zone (kind of virtually isolated network with stricter network policies enforced). Except for incoming traffic through ingress or load balancers, the underlying nodes/servers of Kubernetes cluster are not accessible and are not publicly exposed. Could you please suggest how could we federate these two datacenters together? I was going through this : [https://www.consul.io/docs/k8s/installation/multi-cluster/vms-and-kubernetes#kubernetes-as-the-secondary](https://www.consul.io/docs/k8s/installation/multi-cluster/vms-and-kubernetes#kubernetes-as-the-secondary) And it seems that, it is expected to have two datacenters be able to talk to each other over WAN. But in our case , our Kubernetes cluster is not. Only we could communicate with services running inside kubernetes through Ingress load balancers. ---
**Author:** ![lkysow](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/lkysow/32/1105_2.png) [@lkysow](https://discuss.hashicorp.com/u/lkysow)\ **Post date:** [November 13, 2020, 12:27am UTC](https://discuss.hashicorp.com/t/consul-dcs-federation/17318/2 "2020-11-13T00:27:15Z")
Hi, that guide is the right one to follow. It only requires that mesh gateways have connectivity. The k8s mesh gateway can be a kubernetes load balancer which your VMs should be able to route to.