1
00:00:01,040 --> 00:00:05,040
Migrate IIS Web Apps to Azure Kubernetes Service.

2
00:00:05,040 --> 00:00:08,110
Now, like I warned you at the beginning of this lesson,

3
00:00:08,110 --> 00:00:10,870
the exam is not going to get into the weeds into the

4
00:00:10,870 --> 00:00:14,530
finer points of containerization and AKS,

5
00:00:14,530 --> 00:00:17,180
that's covered under separate certifications.

6
00:00:17,180 --> 00:00:18,910
We don't have the time or the scope.

7
00:00:18,910 --> 00:00:22,340
but absolutely look at the Pluralsight library because

8
00:00:22,340 --> 00:00:26,240
many good friends of mine actually, Anthony Nocentino comes to mind,

9
00:00:26,240 --> 00:00:29,860
have courses on this stuff in the library, and I would trust

10
00:00:29,860 --> 00:00:32,120
anything they have to say on the subject.

11
00:00:32,120 --> 00:00:35,180
Let me give you the Cliff's notes here from a hybrid

12
00:00:35,180 --> 00:00:37,740
cloud administrator's standpoint, alright?

13
00:00:37,740 --> 00:00:39,740
So let's look at step one here.

14
00:00:39,740 --> 00:00:44,360
Your developers want to begin to use these Docker containers to,

15
00:00:44,360 --> 00:00:48,510
instead of building big old monolithic applications that are kind of

16
00:00:48,510 --> 00:00:52,230
difficult to scale and kind of difficult to update and secure,

17
00:00:52,230 --> 00:00:55,820
they want to use Docker tools to create these images that contain

18
00:00:55,820 --> 00:00:58,640
just the application and it's dependencies.

19
00:00:58,640 --> 00:01:02,160
So you might wind up with the three‑tier application with three containers,

20
00:01:02,160 --> 00:01:05,860
one for the database, one for the API, and one for the front end.

21
00:01:05,860 --> 00:01:06,580
You see?

22
00:01:06,580 --> 00:01:08,480
Much more modular way to go,

23
00:01:08,480 --> 00:01:11,640
and the idea when you're using Docker is that we can use the

24
00:01:11,640 --> 00:01:15,090
same tools and images and go to Azure, go to Google,

25
00:01:15,090 --> 00:01:19,830
go to AWS, and go to on‑prem with minimal or no refactoring.

26
00:01:19,830 --> 00:01:23,100
So that's just a nutshell elevator pitch on some of the

27
00:01:23,100 --> 00:01:27,300
benefits of using Docker containers in a microservices

28
00:01:27,300 --> 00:01:29,110
application development context.

29
00:01:29,110 --> 00:01:32,710
Anyway, the developer uses the Docker tools,

30
00:01:32,710 --> 00:01:37,550
including a Docker domain specific language to build out these images.

31
00:01:37,550 --> 00:01:42,550
You've got a plaintext Docker file script that builds or instructs the

32
00:01:42,550 --> 00:01:46,570
Docker build tools how to create this binary deliverable.

33
00:01:46,570 --> 00:01:50,170
This is going to be your application and its dependencies without

34
00:01:50,170 --> 00:01:53,970
all the unnecessary cruft of a virtual machine,

35
00:01:53,970 --> 00:01:57,420
which is the normal alternative to using Docker containers,

36
00:01:57,420 --> 00:01:58,440
alright?

37
00:01:58,440 --> 00:02:00,560
Now that image is the deployable unit,

38
00:02:00,560 --> 00:02:04,640
and we need somewhere for our developers to push or upload those images.

39
00:02:04,640 --> 00:02:05,840
Guess what?

40
00:02:05,840 --> 00:02:07,130
In your Azure subscription,

41
00:02:07,130 --> 00:02:09,590
you have an Azure container registry that gives you

42
00:02:09,590 --> 00:02:11,960
private authenticated access.

43
00:02:11,960 --> 00:02:14,310
You can do digitally signed images,

44
00:02:14,310 --> 00:02:17,570
you can configure vulnerability scanning on those images.

45
00:02:17,570 --> 00:02:20,310
The container registry is a really great product.

46
00:02:20,310 --> 00:02:20,920
Alright.

47
00:02:20,920 --> 00:02:27,140
And then once you're there, you can then run or start containers from that image,

48
00:02:27,140 --> 00:02:30,840
and as you can see, there are a number of services to choose from.

49
00:02:30,840 --> 00:02:33,700
The two that we're concerned with chiefly are app

50
00:02:33,700 --> 00:02:36,160
service and Azure Kubernetes Service.

51
00:02:36,160 --> 00:02:37,900
App service, you might think, wait a minute,

52
00:02:37,900 --> 00:02:40,690
that's what we were just looking at in terms of a code deployment.

53
00:02:40,690 --> 00:02:45,140
Well, as it happens, app service can function with raw code,

54
00:02:45,140 --> 00:02:48,780
but you also can push a container image into it as well.

55
00:02:48,780 --> 00:02:51,440
The issue with that though is that it's not as scalable as

56
00:02:51,440 --> 00:02:55,640
using a full‑fledged cluster orchestrator like Kubernetes

57
00:02:55,640 --> 00:03:04,000
and Azure Kubernetes Service, or AKS, is the native Microsoft Azure hosted implementation of Kubernetes.