Behavior of Ingress Controller

Hello !

My setup is :

  • K8S Cluster
  • Kong + Kong Ingress Controller, connected to Postgres
  • Konga, connected to Kong Admin

If I do make a change on a resource managed by the Ingress Controller through Konga and do not update this ressource on K8S (for example, KongPlugin), the Ingress Controller will erase this change to be in the same state as the K8S resource ?

I just need a confirmation of this behavior, I’m totally okay with it :slight_smile:

Yes. Although, caching in the controller will result in this being delayed.
To disable certain optimizations, use --enable-reverse-sync flag.
Docs: https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/references/cli-arguments.md