 Okay, we are going to talk about trying to access our services. So one of the problems that we have if we do Let's take a look at this cube control Get all So we can see that our services are up and running so we have a pod for our KBE rest You can see that on the third line down there that is up and running our rest services running the services That is on port 8080 the problem that we are running into here as far as accessing that This is I'm going to take a really really complex topic and Try to explain it in a very simplistic way. What's happening is our Kubernetes cluster is creating its own network It's it's like its own virtual network. It's granted. It's running on our machine But one of the tells that you can tell if you're a layperson at networking is we are using Ten dot addresses. So that's an internal IP address that is internal to the kubernetes cluster So if I come in here and do depending on your OS, this command is going to change a little bit especially for Windows So here I'm using IP config and get IF address EN zero so that is for my wireless network card. So the wireless network I can see that I'm on a 192 network So the 192 stanza is different from 10 in other words my network is not set up to talk to that network We don't have a bridge set up. There's no way for network traffic get from point A to point B So even though everything is up Happy in a kubernetes context if we had other services running inside a kubernetes I could talk to each other happily the problem is for me on the command line here I'm outside the cluster. I cannot go in you might go Well, how about if I just go this IP address? That's not going to work when I talk a little over to Postman even though it's running on 8080. That's gonna be the one 27 zero zero dot one address We can see that this is not going to set up there is a utility that we can utilize I'm gonna show you two different ways of getting from network aid and network B We can come back over to the command line and do a clear here and what I can do is say kubectl service kb rust And then I can map 8080 to 8080 Like so and now we can see that I have this this command doesn't come back So that's going to forward that port traffic So it's essentially setting up a tunnel to go from my network to the cluster network Now if I come over here Yeah, have this so I can do a curl So we do have spring boot actuator installed And we can see that we are getting a up status back And when you come back to postman if I run postman now Let's see that I am in fact getting content back from from our spring boot service So that is now working properly the route is established But I come back over to the command line it is established because I have port forwarding we can see that we Got got some chatter there. No if I come in and do a command C that terminates the tunnel If I come back over here run that We see that we failed connect and again if I run in postman that is also going to fail If I were to bring that back up That would Re-enable that so that is one way for testing routes to the Kubernetes cluster is to use this port forward Service or command I should say this is going to be more applicable when you are working Locally with a Kubernetes cluster So there's other techniques as far as exposing services to the world But we're talking about on actual Kubernetes deployments not a single node cluster that we are using to learn on