Konga: [enhancement/feature] Ingress Controller persistence

[andrevtg]

When installed as an Ingress Controller (this is not a bug) Kong only respects configs saved to the cluster as CRDs. This means that it deletes any config set in Konga UI (i.e. it is useless to create resources with Admin API).

A really nice feature for Konga would be the ability to save changes as CRDs into a cluster instead of saving them with Admin API.

The known CRDs are:

• KongConsumer
• KongCredential
• KongPlugin
• KongIngress

[btkelly]

I would also love this feature as it would greatly simplify my Kubernetes setup. If I get some extra time I will try to poke around.

[psucodervn]

Hello everyone. Is there any news about this feature?