# Kong Ingress Controller with existing Kong Instance

**URL:** https://discuss.konghq.com/t/kong-ingress-controller-with-existing-kong-instance/10224
**Category:** General
**Tags:** kong-gateway
**Created:** [May 30, 2022, 6:24am UTC](https://discuss.konghq.com/t/kong-ingress-controller-with-existing-kong-instance/10224 "2022-05-30T06:24:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Seb](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@Seb](https://discuss.konghq.com/u/Seb)
#### Post date: [May 30, 2022, 6:24am UTC](https://discuss.konghq.com/t/kong-ingress-controller-with-existing-kong-instance/10224/1 "2022-05-30T06:24:45Z")

</div>

Hi all,  
I have setup and got a running Kong API Gateway Instance (EE + Manager) in Hybrid Mode (CP/DP split) on EKS.  
I wanted to know if it’s possible to install Kong Ingress Controller with CRDs to interact with that existing Kong Gateway?  
Or there is no choice but to reinstall all from scratch as a controller? And in that case, is the overall config/values completely different?  
Thank you,  
seb.

---

<div class="post-metadata">

### Author: ![Seb](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@Seb](https://discuss.konghq.com/u/Seb)
#### Post date: [May 30, 2022, 8:52am UTC](https://discuss.konghq.com/t/kong-ingress-controller-with-existing-kong-instance/10224/2 "2022-05-30T08:52:44Z")

</div>

Seems this would be achieved by deploying the ingress controller as a standalone node as described in [https://github.com/Kong/charts/tree/main/charts/kong#standalone-controller-nodes](https://github.com/Kong/charts/tree/main/charts/kong#standalone-controller-nodes) ?