WEBVTT 00:00.390 --> 00:05.340 In this demo, we're going to provision a coronets cluster on Microsoft Azure. 00:06.450 --> 00:08.920 So as a prerequisite, you must have and as your account. 00:09.160 --> 00:14.560 And if you're getting started exploring the free access available at this link, so you get twelve months 00:14.560 --> 00:16.060 of free access. 00:16.690 --> 00:24.430 Also, some basic knowledge on Azour can help to, you know, prepare subscriptions and perform some 00:24.430 --> 00:25.600 basic configurations. 00:26.760 --> 00:27.690 So let's get started. 00:28.410 --> 00:32.230 So once you're logged into your Azure account, we see the dashboard. 00:32.550 --> 00:35.040 The basic dashboard provides a list of services. 00:35.160 --> 00:39.840 So here I am using the free account called code cloud, free account. 00:40.380 --> 00:45.840 And what we need to do is either look up for a case which is the edge as your community service. 00:46.290 --> 00:49.090 And in this case, it's already in my list underneath. 00:49.560 --> 00:51.240 And we do not have a cluster created. 00:51.480 --> 00:54.030 So the first thing to do is to add a cluster. 00:54.330 --> 00:57.460 So this will take us to the create communities clusters green. 00:58.050 --> 01:00.690 So it will select your subscription by default. 01:01.350 --> 01:03.870 So make sure the right subscription is selected. 01:03.900 --> 01:07.800 So if you're using a free subscription, make sure that the right one is selected. 01:08.580 --> 01:11.820 So the first thing to do is to create a new resource group. 01:12.540 --> 01:14.100 So I'm going to create a resource group. 01:14.340 --> 01:14.940 We will name it. 01:15.030 --> 01:16.650 Wooding App Resource Group. 01:18.250 --> 01:21.330 And then we're going to name the cluster example voting app. 01:22.500 --> 01:27.930 I'm going to leave the clarinettist version to the default one, which is one dot, one six and for 01:27.930 --> 01:28.860 the node size. 01:29.580 --> 01:32.370 Since this is a free version, I'm going to use just one. 01:32.580 --> 01:35.130 So that's enough for our requirements. 01:35.790 --> 01:38.230 And there are other options that you can edit as well. 01:38.250 --> 01:44.560 So for now, we will just leave most of it to the two, the default values under authentication, said 01:44.610 --> 01:47.430 the service principal, to a new. 01:47.460 --> 01:49.020 So it will create a new one for us. 01:49.920 --> 01:56.370 Service principal is used by the ACA service to manage the cloud resources that are attached to the 01:56.370 --> 01:56.790 cluster. 01:57.780 --> 02:00.390 And next, I'm going to review and create. 02:00.750 --> 02:04.220 So let's wait for it to make the create button available for us. 02:05.530 --> 02:08.830 OK, so once it's available, we can go ahead and click on Create. 02:09.100 --> 02:14.140 So here you will see that it is initializing the deployment of the resource groups first and then it 02:14.140 --> 02:15.760 will create our communities cluster. 02:16.360 --> 02:19.230 So, yeah, this can take some time as well. 02:19.240 --> 02:21.580 So let's just wait for our cluster to be ready. 02:26.130 --> 02:31.140 All right, so now the resources have been deployed and our cluster has been created successfully. 02:31.590 --> 02:37.440 So the next step is to go to the resources that we just created. 02:38.010 --> 02:40.650 And I'm going to type in the voting app here. 02:40.680 --> 02:45.270 So that's just one easy way to get the resource to search for it in the search bar. 02:45.810 --> 02:49.800 So here is our community service and the cluster that we just provisioned. 02:50.140 --> 02:56.040 And to access the cluster, we will make use of the cloud shell, which will open up in the lower half 02:56.040 --> 02:56.700 of the screen. 02:57.390 --> 02:59.910 So in this case, it prompts me to create storage. 02:59.970 --> 03:04.830 So let's just go ahead with it and do that and let's wait for it to complete. 03:04.920 --> 03:07.380 And then we should be able to log into the cloud shell. 03:08.070 --> 03:10.740 So while we wait for that, let's go over the documentation. 03:10.770 --> 03:16.800 So here is the walkthrough of a case which describes the steps that we have been following. 03:16.920 --> 03:22.350 So if we scroll all the way to the bottom, it shows how to connect to the cluster. 03:22.410 --> 03:25.530 So here this is the step that we are trying to do now. 03:25.920 --> 03:29.700 So Cuttle client is preinstalled in the azure cloud shell. 03:30.260 --> 03:31.710 And so we are launching that. 03:31.860 --> 03:38.070 And once the cloud shell is launched, we are going to grant access to keep Cuttle to Arcade's cluster. 03:38.880 --> 03:43.830 So to do that, we have to enter the name of the resource group as well as the name of the cluster that 03:43.830 --> 03:44.550 we just created. 03:44.790 --> 03:49.840 So let's go back to our cloud shell and let's enter the values. 03:49.920 --> 03:55.290 I'm just going to paste the command here and we'll fill in the cluster name. 03:55.800 --> 04:00.000 So the name of the resource group can be copied from the resource group here. 04:05.870 --> 04:09.760 And the name of the cluster, you can copy it from the top here. 04:10.300 --> 04:15.040 So it says example Wooding up because that's the name of the cluster that we just created. 04:15.130 --> 04:21.370 So now the cube config has been set up and we should be able to access the cluster. 04:21.420 --> 04:23.710 So we'll run the cube to get nodes command. 04:24.340 --> 04:28.060 And here we can see that our single node cluster is. 04:28.080 --> 04:31.870 Is visible and is running on wunder one six. 04:31.930 --> 04:33.190 And it is in a ready state. 04:33.820 --> 04:37.720 So just like before, we're going to clone our GitHub repo for our voting app. 04:41.370 --> 04:43.230 So let's run the get clone command. 04:46.740 --> 04:49.020 And once that is done, I'm going to the directory. 04:50.690 --> 04:54.230 And here are all the Yamal files as before. 04:54.890 --> 04:57.230 So let's start creating these services and deployment. 04:57.560 --> 04:59.920 So we will start off with the voting app. 05:00.560 --> 05:04.010 The voting app deployment and then the Voting App Service. 05:04.580 --> 05:10.400 And then we'll go with the red, this deployment and the ready service and the postgrads deployment. 05:10.520 --> 05:12.050 And then the post service. 05:13.070 --> 05:18.140 Next comes the worker deployment and finally deployment and the result service. 05:19.010 --> 05:21.710 So let's check the status of the deployment and services. 05:22.010 --> 05:27.380 And here we see that all the service objects are created except for the result app. 05:27.560 --> 05:28.700 So that's still deploying. 05:29.270 --> 05:33.080 And we already have the load balancer of the external IP for our boarding service. 05:33.950 --> 05:37.160 And the result, services for the wedding service. 05:37.670 --> 05:39.320 And the result services is pending. 05:39.350 --> 05:41.120 So let's just give it a couple of minutes. 05:44.120 --> 05:49.610 All right, so now all our deployments are running and they have one out of one pots for all the five 05:49.820 --> 05:53.750 deployments, and we also have the load balancer for both the result and the voting app. 05:53.750 --> 05:54.110 Ready. 05:54.800 --> 05:58.850 So let's jump into a new tab and let's try to open these applications. 05:59.270 --> 06:03.260 So here I'm on a different window and this is my wedding app. 06:03.800 --> 06:08.030 And let me also open up the result app in a different tab. 06:09.410 --> 06:10.580 So here's the result app. 06:10.790 --> 06:16.330 And let's now cast a vote and we can see that the appropriate results are seen on the result. 06:17.110 --> 06:20.390 And if we change the vote, we can see that it's working as expected. 06:21.410 --> 06:23.210 So that's the end of this demo. 06:23.660 --> 06:31.580 Once you're done with your learning, remember to delete the cluster and clean up the workspace after 06:31.580 --> 06:35.690 you're done so that you can save on some of the credits. 06:36.140 --> 06:37.400 Well, that's it for now. 06:37.780 --> 06:39.370 We'll see you in the next one.