[enhancement/feature] Ingress Controller persistence

pantsel / konga

More than just another GUI to Kong Admin API

MIT License

4.3k stars 826 forks source link

[enhancement/feature] Ingress Controller persistence #319

Open andrevtg opened 5 years ago

andrevtg commented 5 years ago

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 commented 4 years ago

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 commented 4 years ago

Hello everyone. Is there any news about this feature?