# Integrating Kong gateway with existing Istio?

**URL:** <https://discuss.konghq.com/t/integrating-kong-gateway-with-existing-istio/3498>\
**Category:** General\
**Tags:** service-mesh, kong-gateway\
**Created:** [May 13, 2019, 6:32pm UTC](https://discuss.konghq.com/t/integrating-kong-gateway-with-existing-istio/3498 "2019-05-13T18:32:12Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![zhichuanxun](https://avatars.discourse-cdn.com/v4/letter/z/7ea924/32.png) [@zhichuanxun](https://discuss.konghq.com/u/zhichuanxun)\
**Post date:** [November 29, 2019, 8:12am UTC](https://discuss.konghq.com/t/integrating-kong-gateway-with-existing-istio/3498/4 "2019-11-29T08:12:01Z")

</div>

Hi, I got some problem when installing kong above istio in postgresql mode(I have a requirement to use OAuth2), could you help me with that?

> [@Istio sidecar problem](https://discuss.konghq.com/t/istio-sidecar-problem/5002/5):
>
> Hi, I check the installation today and I found it’s not the job problem. Actually, the migration command has done. However, the initcontainer “wait-for-db” in kong cannot run kong start. I exec the container and get the debug info as : Actually, the postgresql can be accessed [image] I don’t know what can I do to fix “unexpected message during auth”.

---

_[View the full topic](https://discuss.konghq.com/t/integrating-kong-gateway-with-existing-istio/3498)._