# Ingress deletion doesn't reflect in postgres in kubernetes hybrid mode **URL:** https://discuss.konghq.com/t/ingress-deletion-doesnt-reflect-in-postgres-in-kubernetes-hybrid-mode/8393 **Category:** General **Tags:** kubernetes **Created:** [May 16, 2021, 6:35am UTC](https://discuss.konghq.com/t/ingress-deletion-doesnt-reflect-in-postgres-in-kubernetes-hybrid-mode/8393 "2021-05-16T06:35:24Z") **Posts on this page:** 1 **Page:** 1
### Author: ![astrobounce](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@astrobounce](https://discuss.konghq.com/u/astrobounce) #### Post date: [May 16, 2021, 6:35am UTC](https://discuss.konghq.com/t/ingress-deletion-doesnt-reflect-in-postgres-in-kubernetes-hybrid-mode/8393/1 "2021-05-16T06:35:24Z")
Hi Team , I am pretty much new to kong , was trying to setup Kong inside kubernetes in hybrid mode for which I have tried to use the below 2 files from examples-values folder minimal-kong-hybrid-control.yaml minimal-kong-hybrid-data.yaml but I can see in minimal-kong-hybrid-control.yaml file **ingressController.enabled is set to false**. I had earlier 2 ingress created inside kubernetes which I can clearly see in postgres > kong=\> select \* from services ; > id | created\_at | updated\_at | name | retries | protocol | host | port | path | co > nnect\_timeout | write\_timeout | read\_timeout | tags | client\_certificate\_id | tls\_verify | tls\_verify\_depth | ca\_certificates | ws\_id ## --------------------------------------±-----------------------±-----------------------±-------------------------±--------±---------±-----------------------------±-----±-----±– --------------±--------------±-------------±--------------------------------±----------------------±-----------±-----------------±----------------±------------------------------ 502456c5-2876-48c5-afb2-903ae5759e8b | 2021-05-15 17:19:30+00 | 2021-05-15 17:19:30+00 | default.bar-service.5000 | 5 | http | bar-service.default.5000.svc | 80 | / | 60000 | 60000 | 60000 | {managed-by-ingress-controller} | | | | | 64534146-a7b9-432c-9fe7-71ff06 2733a8 69284739-b30e-4281-9501-df6528388258 | 2021-05-15 17:29:34+00 | 2021-05-15 17:29:34+00 | default.foo-service.5000 | 5 | http | foo-service.default.5000.svc | 80 | / | 60000 | 60000 | 60000 | {managed-by-ingress-controller} | | | | | 64534146-a7b9-432c-9fe7-71ff06 2733a8 (2 rows) but even after deleting ingress resource I can still see the foo entry inside postgres > Earlier I did setup in standalone mode where ingress controller was also deployed so all entries were created from last iteration of POC . It seems not setting ingressController.enabled to true is one possible reason of this in hybrid mode , can someone please help