# When to use kong ingress? **URL:** \ **Category:** Questions\ **Tags:** kubernetes\ **Created:** [July 8, 2019, 4:00pm UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933 "2019-07-08T16:00:07Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![melkayam92](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@melkayam92](https://discuss.konghq.com/u/melkayam92)\ **Post date:** [July 8, 2019, 4:00pm UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/1 "2019-07-08T16:00:07Z")
Hey, We want to deploy kong as an API gateway (we will need to create consumers dynamically). Is kong ingress is a valid use case for that? or it’s more solution for service mesh? I don’t know wheater to deploy kong as a pod or as ingress. Thanks for the help! ---
**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\ **Post date:** [July 9, 2019, 12:58am UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/2 "2019-07-09T00:58:13Z")
> [@melkayam92](#): > > I don’t know wheater to deploy kong as a pod or as ingress. That depends on how you would like to configure Kong – using Ingress API of k8s or via REST calls to Kong’s Admin API. In either cases, creating consumers dynamically is supported. ---
**Author:** ![melkayam92](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@melkayam92](https://discuss.konghq.com/u/melkayam92)\ **Post date:** [July 9, 2019, 6:45am UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/3 "2019-07-09T06:45:52Z")
Thanks! So the main difference between the two is the the configuration part? ---
**Author:** ![coco](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/coco/32/1179_2.png) [@coco](https://discuss.konghq.com/u/coco)\ **Post date:** [July 9, 2019, 1:52pm UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/4 "2019-07-09T13:52:27Z")
Hi, Is it possible to deploy it as ingress and still use REST calls to create consumers dynamically? ---
**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\ **Post date:** [July 9, 2019, 11:39pm UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/5 "2019-07-09T23:39:01Z")
> [@coco](#): > > Is it possible to deploy it as ingress and still use REST calls to create consumers dynamically? Yes, if you use Kong Ingress Controller[0.5.0](https://github.com/Kong/kubernetes-ingress-controller/blob/master/CHANGELOG.md#050---20190625) and Kong 1.1+ From the 0.5.0 changelog: > **Tagging support** : All entities managed by Kong Ingress Controller in Kong’s database are now tagged and the controller manages only a subset of Kong’s configuration. Any entity created via Kong’s Admin API will not be automatically deleted by the Ingress Controller. Hope that helps. > [@melkayam92](#): > > So the main difference between the two is the the configuration part? Correct, Kong Ingress Controller is simply a different way of configuring Kong. ---
**Author:** ![swapnild2111](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/swapnild2111/32/1197_2.png) [@swapnild2111](https://discuss.konghq.com/u/swapnild2111)\ **Post date:** [July 17, 2019, 9:14am UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/6 "2019-07-17T09:14:29Z")
Can I say if my microservices are deployed in same name space I should use K8s Ingress. And if I want to use third party API hosted publicly, I should not go for KongIngress? Please correct me 🙂 ---
**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\ **Post date:** [July 23, 2019, 1:00am UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/7 "2019-07-23T01:00:03Z")
> [@swapnild2111](#): > > Can I say if my microservices are deployed in same name space I should use KongIngress. > And if I want to use third party API hosted publicly, I should not go for KongIngress? That’s not entirely correct. If you need fine-grained control over the proxy behavior, more than what the Ingress API offers, you will need to use KongIngress resource. ---
**Author:** ![swapnild2111](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/swapnild2111/32/1197_2.png) [@swapnild2111](https://discuss.konghq.com/u/swapnild2111)\ **Post date:** [July 23, 2019, 9:01am UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/8 "2019-07-23T09:01:48Z")
So if I start using KongIngress - it can access my cluster local namespaced services + external services? ---
**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\ **Post date:** [July 24, 2019, 4:50pm UTC](https://discuss.konghq.com/t/when-to-use-kong-ingress/3933/9 "2019-07-24T16:50:27Z")
KongIngress has nothing to do with it. With the regular Ingress, you can use local + external service.