Hey guys!
We are currently thinking about implementing an API gateway and Kong was the choice.
In our structure we have a reverse proxy (Nginx) that receives all external requests from customers and partners.
We have APIs that run on Kubernetes and others on IIS and that sometimes communicate with each other. For now, we have about 10 APIs in production but this number tends to grow every day.
What would be the best approach to deploy Kong?
In a separate Kubernetes cluster?
In the same Kubernetes cluster but in a different namespace?
In a VM?
Does Kong support SQL Server?
Suggestions for SSO? We are considering Keycloak
PS.: We are only considering community versions for the moment
Your question regarding Kong Gateway deployment is challenging to answer because the best deployment option is heavily dependent on your specific requirements and system structure. If you wish to enumerate any concerns or specifics, I might be able to help you get further guidance.
Does Kong support SQL Server?
Kong Gateway only supports PostgresSQL at this time. An alternative for you to consider is Kong Konnect (Kong Konnect | Kong Docs) which frees you from the burden of running a DB entirely.
Suggestions for SSO? We are considering Keycloak
The OpenID Connect plugin documentation provides a list of supported and tested IdP providers, which includes Keycloak!