1
00:00:03,850 --> 00:00:04,910
All right.

2
00:00:04,920 --> 00:00:09,930
We tried rolling updates and also we tried to delete one of the one inputs.

3
00:00:09,930 --> 00:00:14,250
And now let me demonstrate to you how to launch Kubernetes dashboard.

4
00:00:14,460 --> 00:00:18,510
If you are using mini cube, it is very easy, just single command.

5
00:00:18,690 --> 00:00:24,750
But if you are running Kubernetes on your own premises or somewhere in the cloud, it could be a bit

6
00:00:24,750 --> 00:00:30,300
more difficult because you need to secure web access to Dashboard.

7
00:00:30,300 --> 00:00:35,250
But here again, this is just a single command mini cube dashboard.

8
00:00:36,640 --> 00:00:37,420
Like that.

9
00:00:37,450 --> 00:00:39,220
Let's enable this broad.

10
00:00:40,140 --> 00:00:42,600
Launching proxy will define proxy health.

11
00:00:44,410 --> 00:00:48,370
And this broad Web page will be opened here.

12
00:00:49,520 --> 00:00:54,650
And as you saw here, no prompt for username and password.

13
00:00:54,650 --> 00:01:02,030
This dashboard was simply launched like that because we are using mini cube and here you could observe

14
00:01:02,060 --> 00:01:05,900
details about your Kubernetes cluster, for example.

15
00:01:05,900 --> 00:01:10,000
You could go to deployments and you will find a single deployment here.

16
00:01:10,000 --> 00:01:13,820
What is let me decrease a bit font size like that.

17
00:01:13,820 --> 00:01:16,970
So here is metadata for this deployment.

18
00:01:17,120 --> 00:01:20,990
Here are labels strategy rolling update.

19
00:01:21,080 --> 00:01:22,550
That's what we observed.

20
00:01:23,660 --> 00:01:26,570
Board status for available for updated.

21
00:01:27,940 --> 00:01:35,320
Here are conditions new replica set here with ID of the replica set which was created by this deployment.

22
00:01:35,350 --> 00:01:40,300
You could click on this hyperlink and read details about specific replica set.

23
00:01:41,530 --> 00:01:47,280
Notice that replica set deployment and ports all belong to the same namespace default.

24
00:01:47,290 --> 00:01:55,980
But of course you could assign deployments to different custom namespaces labels for this replica set

25
00:01:55,990 --> 00:01:59,050
port status for running for desired.

26
00:01:59,050 --> 00:02:04,900
And here are links to all ports which belong to this particular replica set.

27
00:02:05,140 --> 00:02:11,450
Also below there was service which was created for this replica set for this deployment.

28
00:02:11,470 --> 00:02:13,840
Type is a load balancer here.

29
00:02:15,380 --> 00:02:20,120
And if you click on specific port, you could read details about particular port.

30
00:02:20,150 --> 00:02:24,590
Here is name of the port namespace when port was created.

31
00:02:24,620 --> 00:02:28,880
Here is information about the node where this port was created.

32
00:02:28,880 --> 00:02:30,210
Status is running.

33
00:02:30,230 --> 00:02:32,650
IP address of the port below.

34
00:02:32,660 --> 00:02:38,960
You could also find details about replica set which actually controls this particular port.

35
00:02:39,500 --> 00:02:45,400
And notice that the label for this port is here up on Kate's web.

36
00:02:45,410 --> 00:02:46,000
Hello.

37
00:02:46,010 --> 00:02:54,350
And the same label is found here controlled by replica set and heroes label in the replica set.

38
00:02:55,570 --> 00:03:01,600
Also below, you might find details about events which happened in this particular report.

39
00:03:01,720 --> 00:03:05,290
For example, here is a step pulling image.

40
00:03:05,290 --> 00:03:07,180
Bicester UK s web.

41
00:03:07,180 --> 00:03:07,780
Hello.

42
00:03:08,700 --> 00:03:13,470
And here are details about containers which are now running inside of the port.

43
00:03:13,860 --> 00:03:17,430
There is now just a single container inside of each port.

44
00:03:17,940 --> 00:03:25,260
By the way, if I go to replica sets, I will find actually two different replica sets which were created

45
00:03:25,260 --> 00:03:29,570
for different images for this image and for this image.

46
00:03:29,580 --> 00:03:37,920
And now in this replica set, there are zero ports because we rolled back from this image to this image

47
00:03:37,920 --> 00:03:39,200
with tech latest.

48
00:03:39,210 --> 00:03:43,710
That's why now here I see four ports and here are zero ports.

49
00:03:44,730 --> 00:03:45,270
Alright.

50
00:03:45,270 --> 00:03:52,260
This graphical user interface, you could click on other menu items and observe which for example,

51
00:03:52,260 --> 00:03:54,030
nodes belong to the cluster.

52
00:03:54,060 --> 00:03:56,610
Now there was just a single mini cube node.

53
00:03:57,510 --> 00:04:04,500
And if you click on it, you could read the details about this particular node that was Kubernetes dashboard,

54
00:04:04,500 --> 00:04:09,930
and you could utilize it in order to observe status of the Kubernetes deployments and services and so

55
00:04:09,930 --> 00:04:10,260
on.

56
00:04:10,980 --> 00:04:11,850
Let me close it.

57
00:04:11,850 --> 00:04:13,710
And now let's continue.

58
00:04:13,710 --> 00:04:19,290
And the less controls see, in order to interrupt this process here and now, meaning Kubernetes brought

59
00:04:19,290 --> 00:04:21,779
will not be available anymore.