The developer configures multiple Kubernetes microservices including notifications, payments, auth, and reservations. Actions include updating YAML deployment files, creating Kubernetes secrets for sensitive keys, setting environment variables, generating cluster IP services, and deploying upgrades via Helm.
Length 13:23
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #kubernetes #deployment #services #secrets #microservices #yaml #helm #backend #coding #terminal
0:00 Okay, let's go ahead and head back to the deployment.yaml for 0:04 the 0:04 notification service, where we're gonna go ahead and add some 0:08 environment variables for this deployment. 0:11 And let's go ahead and define a new field here called ports, 0:15 and define a container port. So this is going to be 0:19 the port that we're going to allow connections on inside of this pod. 0:24 In this case, we will use port three thousand. 0:26 So now we've told Kubernetes which port we're connecting on, 0:30 we need to tell 0:30 the actual pod itself through the environment variable. 0:34 Let's go ahead and do this with the environment variable section, and we'll 0:38 go ahead and define a new environment variable name port, and 0:42 we'll provide the value at port three thousand. 0:45 Next, we need to provide our Google OAuth 0:47 environment variables. 0:49 So let's go ahead and provide the ones 0:51 that don't need to be secret 0:53 first. We'll start off with the Google 0:57 OAuth client ID and set the value 1:00 equal to the .env from our 1:04 notifications.env file. We can copy this 1:07 value over 1:10 and paste it in as plain text. 1:14 We can do the same thing for the SMTP 1:18 user. 1:19 We'll go ahead and set the value from our .env 1:23 file 1:25 as the sleepernestapp@gmail.com. 1:29 Now we need to create two secrets for our client 1:32 secret as well as the refresh token as these are sensitive values. 1:37 So we'll create these secrets the same way we have before by running 1:40 kubectl create secret, and I'll call this Google. 1:45 Then we're going to specify from literal and 1:49 set equals client secret, and 1:53 set that equal to the client secret 1:58 from our .env file, 2:00 and we'll simply paste this in. 2:03 Then we'll go ahead and, and add another from literal flag where 2:06 we'll 2:07 set the refresh token key equal
The rest of the transcript is for members.
Sign in 