So let's also check ports.
K get ports.
Some of the boats are running and one is still pending.
And now we are able to test our setup and try to connect from web application, from Web deployment
to engine deployment.
Let's open connection to our Web service deployment because we used here a load balancer type for this
service and we could utilize this port here and IP address of the Kubernetes node.
We kept that in order to quickly get a URL for specific deployment using mini cube, you could enter
command, mini cube service and here we'll be name of the service k8s web two and Genesis.
Web browser page was opened and we got response from one of the posts which belongs to k8s web to engine
deployment.
And here was name of the corresponding replica set.
All right.
We just triggered a connection to route URL.
Let's go back quickly to our application.
Let me hide this terminal here and let's go to this new application and open index, both file and request
that here we have two endpoints root endpoint and slash and endpoint, which will essentially send request
to engineers your well, this one and return back to the client proxy response from our other server.
This server is external relative to this server where we are running this web application.
We just received this string from the server.
Let's not try to connect to an endpoint.
Let's go back to web browser and add here.
Slash and J.
Nicks.
Press enter.
And what I got, I got.
Welcome to N Jennings.
It means that the response from the Phoenix Sarah was broadcast successfully inside of the server,
which belongs to our web deployment.
And we were able in such a way to connect from one deployment to another deployment.
By the name of another service.
So NCLEX here is the name of another service as we specified here.
And such service has no cluster IP.
They get, as we see.
So here is cluster IP for angelic service.
And we were able to connect to another deployment by name of the service.
That's how you could very easily connect different deployments together.