1

00:00:02,460 --> 00:00:06,690

Now that a cluster is ready, let's deploy communities dashboard in it.



2

00:00:07,290 --> 00:00:12,030

In order to do that, we're going to go back to a command line and execute KIPP's.



3

00:00:12,030 --> 00:00:19,710

It'll apply and pass it a file which is actually remotely hosted.



4

00:00:20,280 --> 00:00:22,230

So this is from communities itself.



5

00:00:22,560 --> 00:00:28,680

And this Yamal basically includes the configuration of all the components that need to be deployed for



6

00:00:28,680 --> 00:00:29,670

communities dashboard.



7

00:00:29,940 --> 00:00:35,480

It includes the user permissions, the dashboard application itself and so on.



8

00:00:35,940 --> 00:00:39,410

So you don't have to worry about creating all this stuff yourself.



9

00:00:39,600 --> 00:00:43,310

We just execute this file and it creates all the necessary components.



10

00:00:43,740 --> 00:00:49,620

And by the way, all the commands that I'm using in this course will be also in a good repository,



11

00:00:49,770 --> 00:00:50,850

in a separate file.



12

00:00:51,060 --> 00:00:54,530

So you can check that in the link and copy them directly from there.



13

00:00:54,990 --> 00:00:56,940

So I'm going to execute this command.



14

00:00:58,210 --> 00:01:04,480

And you see that it created a bunch of components like Secret Service account namespace and so on,



15

00:01:04,600 --> 00:01:08,520

and basically Dashboard's is deployed in the cluster.



16

00:01:08,710 --> 00:01:10,210

We just have to access it now.



17

00:01:10,510 --> 00:01:14,040

So here you see a namespace crudities Dysport got created.



18

00:01:14,380 --> 00:01:17,740

So we are going to check in that namespace.



19

00:01:17,740 --> 00:01:20,500

So minus N stands for namespace.



20

00:01:21,070 --> 00:01:24,890

This dashboard, we're going to check what pots are running inside.



21

00:01:25,330 --> 00:01:31,270

So this is our communities dashboard application and this is the metric scraper, which is the metrics



22

00:01:31,270 --> 00:01:37,960

data scraper for tools like Prometheus and other similar monitoring tools for these course, it is not



23

00:01:37,960 --> 00:01:42,540

interesting for us, but now we have to access that application from outside.



24

00:01:42,850 --> 00:01:51,700

And the way we do that just locally is we are going to execute Cusato proxy and this will basically



25

00:01:51,700 --> 00:01:57,640

proxy the endpoints to our local machine so we can access them through localhost.



26

00:01:57,940 --> 00:02:01,640

And each application obviously will have its own endpoint.



27

00:02:02,110 --> 00:02:08,450

This is the endpoint for Dashboard, so you can also copy that from the provided good story.



28

00:02:08,740 --> 00:02:14,260

So here you see the dashboard view is secured, but we can easily get access using the cube config.



29

00:02:14,440 --> 00:02:19,650

And this is the same file as we downloaded from the cluster, which is this one here.



30

00:02:19,660 --> 00:02:24,580

So you can upload it from your downloads and you can sign in with this one.