Multiple Microservice Backends to a Singular Public API endpoint

[tsan]

We are working on a unified, public API endpoint (e.g. api.myapi.com) with many backend services (running as GKE services) being mapped to that same public API endpoint (api.myapi.com).  Each backend service is a microservice and needs to be run independently on the Kubernetes cluster.  We are using OpenAPI.  I have yet to find anything that clearly shows that this is possible.  Any ideas?

[Rene Figueroa]

I put other ngnix up front each container esp and each service dns pointing to each esp. and each esp to each microservice. at the end of the day. i have 6 microservices with 6 esp's and one ngnix. i'm planning change this ngnix for google load balancer in futher. 

I dont know, that is correct. 

[Wencheng Lu]

yes, l7 gce loadbalancer is the recommend approach at this moment: https://github.com/GoogleCloudPlatform/endpoints-samples/tree/master/k8s#using-gce-l7-load-balancer-with-esp

https://github.com/GoogleCloudPlatform/endpoints-samples/blob/master/k8s/esp_echo_gke_ingress.yaml

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endpoints+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/ea3d6404-0f2b-4f61-b6ee-c88bd0549483%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[tsan]

I am already using the GCE L7 LoadBalancer with GCE Kubernetes Ingress.  The ESP sidecar proxy doesn't seem to have a feature to be able to unify multiple backend Kubernetes services into a singular API endpoint on the GCE L7 LoadBalancer.  This is a very important feature in my opinion.  Without it, each service essentially needs it's own public api endpoint and that gets ugly fast with multiple related backend services.  Kong API proxy is able to do it by examining the incoming hostname and/or URI paths and map to any arbitrary upstream (service) endpoint.

[Dan Ciruli]

Tyler -

We are working on a solution for exactly the problem you are trying to solve, and we'd love to talk to you a bit more in depth.

Do you mind if I email you directly to set something up?

DC

On Wed, Oct 25, 2017 at 3:44 PM, tsan <tylers...@gmail.com> wrote:

I am already using the GCE L7 LoadBalancer with GCE Kubernetes Ingress.  The ESP sidecar proxy doesn't seem to have a feature to be able to unify multiple backend Kubernetes services into a singular API endpoint on the GCE L7 LoadBalancer.  This is a very important feature in my opinion.  Without it, each service essentially needs it's own public api endpoint and that gets ugly fast with multiple related backend services.  Kong API proxy is able to do it by examining the incoming hostname and/or URI paths and map to any arbitrary upstream (service) endpoint.

On Wednesday, October 25, 2017 at 4:53:15 PM UTC-5, Wencheng Lu wrote:

yes, l7 gce loadbalancer is the recommend approach at this moment: https://github.com/GoogleCloudPlatform/endpoints-samples/tree/master/k8s#using-gce-l7-load-balancer-with-esp

https://github.com/GoogleCloudPlatform/endpoints-samples/blob/master/k8s/esp_echo_gke_ingress.yaml

On Wed, Oct 25, 2017 at 1:43 PM, Rene Figueroa <re...@axtop.io> wrote:

I put other ngnix up front each container esp and each service dns pointing to each esp. and each esp to each microservice. at the end of the day. i have 6 microservices with 6 esp's and one ngnix. i'm planning change this ngnix for google load balancer in futher. 

I dont know, that is correct. 

On Tuesday, October 24, 2017 at 8:25:21 PM UTC-5, tsan wrote:

We are working on a unified, public API endpoint (e.g. api.myapi.com) with many backend services (running as GKE services) being mapped to that same public API endpoint (api.myapi.com).  Each backend service is a microservice and needs to be run independently on the Kubernetes cluster.  We are using OpenAPI.  I have yet to find anything that clearly shows that this is possible.  Any ideas?

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endpoints+unsubscri...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/ea3d6404-0f2b-4f61-b6ee-c88bd0549483%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endpoints+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/a59c829b-30f1-4176-900d-139dd2e907da%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

DC

[Glenn Jones]

We interested in the something very similar and we are currently going with the approach outlined by Rene FIgueroa on this thread.

If there are other alternatives to consider or maybe a tutorial/example that could be shared, that would be very helpful.

Thanks,

Glenn

On Tuesday, October 24, 2017 at 8:25:21 PM UTC-5, tsan wrote:

[ral...@webdox.cl]

We setup a Google Load Balancer and then setup multiple backends to each service by having individual NodePorts for each service. Has worked well for us - it's somewhat cumbersome though.