1 00:00:01,710 --> 00:00:06,280 In this video, we're going to create two secrets that are required for our application to run inside 2 00:00:06,280 --> 00:00:07,630 of our digital ocean cluster. 3 00:00:08,350 --> 00:00:12,990 So the two secrets we have to provide are a secret named JWT Dasch secret. 4 00:00:13,150 --> 00:00:17,990 And that's going to contain a property of GW Tiki and the other one that I had completely forgot. 5 00:00:18,050 --> 00:00:19,980 And the last video was Stripe Secrets. 6 00:00:20,380 --> 00:00:23,770 That's going to contain a secret or a property called Stripe Underscore Key. 7 00:00:25,080 --> 00:00:30,090 If you vacate where that strike comes from, member, you're going to go to a dashboard striped ICOM 8 00:00:30,630 --> 00:00:31,320 on the left hand side. 9 00:00:31,350 --> 00:00:36,150 We can find developers API keys and we're going to look for secret key right there. 10 00:00:36,360 --> 00:00:39,300 You can click Reveal Test Key Tolkan to show your key. 11 00:00:42,100 --> 00:00:45,730 So once we get that key, we're going to create our two secrets. 12 00:00:45,800 --> 00:00:47,710 Remember, we create secrets from the command line. 13 00:00:48,690 --> 00:00:54,290 So back at the command line, we're going to use QCT T.L. to access our digital ocean cluster. 14 00:00:54,770 --> 00:01:00,950 That means we need to make sure that our QC, T.L. is configured to use our context or digital ocean. 15 00:01:01,740 --> 00:01:07,060 It a reminder on what context you're using right now, you can very easily go back up to your system 16 00:01:07,060 --> 00:01:07,480 tray. 17 00:01:07,900 --> 00:01:10,570 Take a look at communities and see which one you're connected to. 18 00:01:11,230 --> 00:01:16,540 Alternatively, if you are not using Docker desktop, remember, you can always do a QVC T.L. config 19 00:01:16,610 --> 00:01:17,000 view. 20 00:01:18,010 --> 00:01:20,020 That's going to show you all the different things are running. 21 00:01:21,390 --> 00:01:22,530 We can look at contexts. 22 00:01:23,480 --> 00:01:25,670 I want to find my digital ocean context. 23 00:01:25,800 --> 00:01:26,930 So that's my name right there. 24 00:01:28,410 --> 00:01:35,580 All then do a cube CDL config, use context, and I'll paste in the name of my digital ocean context. 25 00:01:36,570 --> 00:01:37,530 And that switches me over. 26 00:01:40,000 --> 00:01:43,960 Now we're going to run the command to manually create a secret on our digital ocean cluster. 27 00:01:44,560 --> 00:01:46,800 We'll first create the Jason Web tokin secret. 28 00:01:47,170 --> 00:01:48,580 We're going to do a cube CTO. 29 00:01:49,270 --> 00:01:50,410 It's create secret. 30 00:01:51,830 --> 00:01:53,510 Then generic. 31 00:01:54,930 --> 00:01:58,830 Then the name of our secrets, which is a JWT Dasch secret. 32 00:01:59,910 --> 00:02:02,040 Then Dash Dash from Litoral. 33 00:02:03,490 --> 00:02:04,000 Equals. 34 00:02:04,360 --> 00:02:07,840 And now we're going to enter in our key value pair right here without any spaces. 35 00:02:08,500 --> 00:02:12,710 So our key is supposed to be JWT under squawky equals. 36 00:02:13,450 --> 00:02:15,850 And then whatever value we want to assign to this. 37 00:02:16,300 --> 00:02:19,980 Remember, it is supposed to be a random stream of characters that are going to somehow sign our days 38 00:02:19,980 --> 00:02:23,740 on Web tokens like an entry and just some random stream characters like so. 39 00:02:23,800 --> 00:02:25,060 And that should be good enough. 40 00:02:26,270 --> 00:02:27,020 Kate looks good. 41 00:02:28,400 --> 00:02:30,550 Our second secret for the striped key. 42 00:02:31,130 --> 00:02:36,220 This one is supposed to have a name of stripe dash secret and then a key of stripe key. 43 00:02:37,740 --> 00:02:41,250 And then finally, our value once again is going to come from our dashboard back over here. 44 00:02:44,140 --> 00:02:45,370 Tobacco over at our terminal. 45 00:02:46,150 --> 00:02:50,950 We're going to do a deal, create secret generic. 46 00:02:51,550 --> 00:02:53,770 The name of the secret is going to be stripe secret. 47 00:02:55,020 --> 00:02:57,120 Well, then, specify from literal. 48 00:02:58,470 --> 00:02:59,070 Equals. 49 00:02:59,550 --> 00:03:03,190 The key that we want to set inside the secret is stripe underscore key. 50 00:03:03,690 --> 00:03:06,030 And then the value of that is going to be the key. 51 00:03:06,090 --> 00:03:07,890 Often for our stripe dashboard itself. 52 00:03:08,840 --> 00:03:12,050 Now, once again, extremely important that you type out the secrets. 53 00:03:12,150 --> 00:03:16,080 Exactly as I show it, to make sure the secrets name is Stripe's Secret. 54 00:03:16,560 --> 00:03:18,180 Make sure you've got a key inside there. 55 00:03:18,340 --> 00:03:20,910 Start key and a value of your secret key. 56 00:03:21,810 --> 00:03:26,280 Once you've got that all put together, we'll run that and we should see that the secret was created. 57 00:03:27,150 --> 00:03:27,370 OK. 58 00:03:28,200 --> 00:03:28,890 So this looks good. 59 00:03:29,370 --> 00:03:33,840 Now, the last thing that we really have to do before we do a quick test of merging in April request 60 00:03:34,140 --> 00:03:36,660 you do a little bit of setup on ingress, engine X. 61 00:03:37,050 --> 00:03:38,790 They're going to take care of that in just a moment.