@hbagdi Not looking to use kong as ingress controller to k8s yet! Before we actually use kong as an ingress controller to k8s, we would want to deploy it as a service on k8s leveraging the authentication plugin and have phase-wise migrations of services to kong.
- Are there any issues you see with approach?
- Kong would be k8s service in this case with moderate to high load on auth plugin. AFAIK, the basic auth plugin caches basic auth credentials on kong nodes, so load on DB shouldn’t be high. Please correct me if wrong.
@mike.roth +1. I had the same question that I asked a few months back, but couldn’t follow up on the same. Kong ingress controller and custom CRDs