0:00 Okay, so our last step is to create a service for reservations, 0:04 and this 0:04 is the most important one because it's going to be what our users 0:07 are going to use 0:08 to actually enter our system and make calls to create 0:11 reservations and trigger our whole application. 0:15 In this sense, it's acting like the API gateway, 0:18 and this service is what we're 0:19 going to need to actually expose externally. 0:22 Now, when we run this service in Google Cloud, 0:25 we're actually gonna provision 0:26 a load balancer. However, when we're running locally, we just wanna 0:30 configure it as a NodePort service so that we can communicate it 0:34 via local host. Let's go ahead and set this up. 0:38 We'll CD into the templates directory, into reservations, 0:42 and we can run our usual command to create a service. 0:44 To change the service type here now to be NodePort. 0:48 We'll still specify a TCP and expose it on 0:51 3004. We can set dry run equal to client, 0:55 output YAML, and of course, don't forget the name of the service as 0:59 well, 1:00 which we'll call reservations. And we'll go ahead and pipe this out to 1:04 a service.yaml as usual. So now in the reservations 1:08 folder, we can see our service, and we will remove the load balancer 1:11 and the creation timestamp as usual. 1:14 So one last improvement we're gonna make to make our services a bit cleaner 1:18 is to actually in... update the name. 1:20 So if it's a microservice, we'll leave the name as TCP, 1:24 otherwise, we'll call the name HTTP. 1:27 So let's go ahead and update our services and payments. 1:31 In payments, we know this is a TCP microservice port. 1:34 We'll call it TCP. In notifications, we'll go ahead and 1:38 do the same. It's TCP. And most importantly, in auth, this is 1:42 where it'll be most clear. The TCP port is at
The rest of the transcript is for members.
Sign in 