snert:istio hrupp$ curl http://istio-ingressgateway-istio-system.192.168.64.19.nip.io/mp-servicemesh-sample/serviceA
Hello from serviceA (org.eclipse.microprofile.servicemesh.servicea.ServiceAEndpoint$Proxy$_$$_WeldSubclass@5b82d4b3)
Calling service at: http://serviceb-service:8080/mp-servicemesh-sample/serviceB (ServiceA call count: 19, tries: 1)
Hello from serviceB (org.eclipse.microprofile.servicemesh.serviceb.ServiceBEndpoint$Proxy$_$$_WeldSubclass@2a067b42) at Fri Jul 27 13:53:47 UTC 2018 on serviceb-deployment-5b684b7bb8-kmgng (ServiceB call count: 18, failFrequency: 10)
snert:istio hrupp$ curl http://istio-ingressgateway-istio-system.192.168.64.19.nip.io/mp-servicemesh-sample/serviceA
Hello from serviceA (org.eclipse.microprofile.servicemesh.servicea.ServiceAEndpoint$Proxy$_$$_WeldSubclass@2f475f5a)
Calling service at: http://serviceb-service:8080/mp-servicemesh-sample/serviceB (ServiceA call count: 20, tries: 1)
Hello from serviceB @ Fri Jul 27 13:53:50 UTC 2018 org.eclipse.microprofile.servicemesh.serviceb.ServiceB@ab6b99e6 on serviceb-liberty-deployment-564c7588fd-6zr26, failProbablibity: 0.0snert:istio hrupp$
We should try to expose the server kind (Thorntail, Liberty, ... ), while e.g. hostname is in my opinion less interesting. Here for liberty it luckily includes the string "liberty", but that is arbitrary because I tagged the image with that name
Currently the situation is as follows:
We should try to expose the server kind (Thorntail, Liberty, ... ), while e.g. hostname is in my opinion less interesting. Here for liberty it luckily includes the string "liberty", but that is arbitrary because I tagged the image with that name