Microservices Api gateway and Identity Server 4 kubernates

It sounds like your question is related to Service Discovery.

In Kubernetes, the native way an "API Gateway" is implemented, is by using Ingress resources and Ingress Controllers. If you use a cloud provider, they usually have a product for this, or you can use a custom deployed within the cluster.

Service Discovery the Kubernetes way, is by referring to Service resources, e.g. the Ingress resources maps URLs (in your public API) to services. And your app is deployed as a Deployment resource, and all replicas (instances) is exposed via a Service resource. An app can also send request to other apps, and it should address that request to the Service resource for the other app. The Service resource does load balancing to the replicas of the receiving app.

you can use the service name to connect with the service instead of the client IP.

for example : curl HTTP://<service.name>.<namespace name>.svc.cluster.local

now if you are looking forward to list of API gateway and Identity server for Kubernetes

there are several options however it all depends on requirement.

For basic requirement nginx ingress and other ingress is available while if you are looking for API gateway :

• Kong APi gateway
• Ambassador api gateway
• TYK API gateway

part of that service mesh can be also useful not in all scenario because it's mostly used for managing internal traffic (east-west).

API gateway is mostly used for managing edge traffic.

List of identity servers :

• keycloak
• Cognito IAM (AWS)

ingress controllers :

• GCE ingress
• Nginx ingress controller
• Kong ingress controller
• Gloo
• HA proxy
• AKS gateway
• istio ingress