# Installing Kong for K8s enterprise (DB-less) in Distributed Environment

**URL:** https://discuss.konghq.com/t/installing-kong-for-k8s-enterprise-db-less-in-distributed-environment/9193
**Category:** Questions
**Created:** [October 17, 2021, 8:27am UTC](https://discuss.konghq.com/t/installing-kong-for-k8s-enterprise-db-less-in-distributed-environment/9193 "2021-10-17T08:27:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Sachin\_Ghumbre](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/sachin_ghumbre/32/2737_2.png) [@Sachin\_Ghumbre](https://discuss.konghq.com/u/Sachin_Ghumbre)
#### Post date: [October 17, 2021, 8:27am UTC](https://discuss.konghq.com/t/installing-kong-for-k8s-enterprise-db-less-in-distributed-environment/9193/1 "2021-10-17T08:27:45Z")

</div>

In Kong for Kubernetes Enterprise (DB-less) and for Distributed installation type, we need to install more than one nodes with the steps given in below url.

> **[Install on Kubernetes - Kong Gateway - v2.8.x | Kong Docs](https://docs.konghq.com/gateway/2.6.x/install-and-run/kubernetes/)**
>
> Documentation for Kong, the Cloud Connectivity Company for APIs and Microservices.

If I perform above configuration steps say on 3 different nodes, it will form a distributed environment cluster of 3 nodes. Now assume I created one service and deployed it in first node using kubectl command. Since there is no CP/DB, how that service deployed in one node will be synched with other nodes ?

---

<div class="post-metadata">

### Author: ![traines](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/traines/32/158_2.png) [@traines](https://discuss.konghq.com/u/traines)
#### Post date: [October 18, 2021, 6:49pm UTC](https://discuss.konghq.com/t/installing-kong-for-k8s-enterprise-db-less-in-distributed-environment/9193/2 "2021-10-18T18:49:42Z")

</div>

When you’re using the ingress controller, an instance of the controller runs alongside each instance of the Kong proxy. Each controller instance will generate and apply the same configuration from Kubernetes resources, so while there’s no direct communication between instances, they’ll all receive the same set of configuration.
