Hi, The first way to do it is as you have already stated, exposing the deployment. The other way I recommend is using Istio [1]. Istio helps create a multi cluster mesh on a shared network to allow communication between the clusters. I would suggest reading the attached article and see if this can help in regards to your use case.
[1] https://istio.io/latest/docs/concepts/what-is-istio/ On Friday, August 14, 2020 at 10:28:08 AM UTC-4 luca...@icloud.com wrote: > Hi There, > > I have 2 clusters: cluster A and cluster B. > > I have an app A running on cluster A (docker container) and an app B > running on cluster B (docker container). > > All instances of app B needs to send messages (REST API) to app A and I > want that to be happening using the app hostname (the one google Kubernetes > assigns to each pod of a deployed app) but the host cannot be resolved > apparently because app A fails to reach app B using app B hostname. > > Any idea what I need to do here? Note that I can expose a load balancer > and that works BUT I really need to reach individual pods here. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/cdc51599-157a-4d9f-aa88-65daef557da4n%40googlegroups.com.
