We currently have an architecture that results in X number of Kubernetes cluster that have the same applications deployed for resilience. We are using kong as our ingress controller in both of these clusters without any issues. It is also important to note that currently we have two seperate databases for each Kong/cluster combination. My question comes from us wanting to use Kong to also handle our authentication layer, currently our application handles that. However, if we were to move the authentication layer into Kong ( we use the ingress controller deployment method) then we would have to make sure that the consumer is replicated per cluster.
Is it possible to / Do you see any issues with using the same database for both Kong instances and insert consumers into the database instead of using the KongConsumer CRD?
If not, then what would the best practice be for accomplishing the above? Do we just need to make sure every cluster is in sync with the consumer object by making the call for every cluster when adding consumers?