I am currently using the KongIngress in association with KongConsumer and KongCredential and I am taking an approach similar to One Consumer per user.
I wonder, to have a correct user management, I’m planning to have an active directory (like LDAP) without using the plugin (my workflow is kind of weird).
So I will probably have to map my consumer and my users (via custom_id) and to create a new consumer when I create a new User (probably using 2PC) .
The main problem (for me) using kong as an ingress and not as an app here is I will have to dynamically update kubernetes via Kubernetes-API to create/update consumer. Isn’t it evil? In this case, shouldn’t I use Kong as an app?
For me, Kubernetes configuration must be versionned, but here I have dynamic update so I can’t version it, so it will look kind of awkward to have some of my kubernetes conf installed and some are not.