1
00:00:00,940 --> 00:00:05,730
There's not a whole lot on continuous integration/continuous delivery on AZ‑800,

2
00:00:05,730 --> 00:00:08,110
just little hints of it here and there.

3
00:00:08,110 --> 00:00:10,720
This is an architectural diagram that shows one of

4
00:00:10,720 --> 00:00:12,330
Microsoft's reference architectures,

5
00:00:12,330 --> 00:00:16,450
this one showing how you could possibly implement some of the

6
00:00:16,450 --> 00:00:19,760
Azure container tools in a CI/CD process.

7
00:00:19,760 --> 00:00:23,120
But we have our engineer using their tools,

8
00:00:23,120 --> 00:00:26,070
whatever it might be, Visual Studio in this example,

9
00:00:26,070 --> 00:00:29,500
committing code changes to a central Git repository.

10
00:00:29,500 --> 00:00:33,730
Now this example assumes that the team is using Azure DevOps.

11
00:00:33,730 --> 00:00:36,320
Normally, you would have your pipeline,

12
00:00:36,320 --> 00:00:39,770
your build pipeline set to auto trigger when a

13
00:00:39,770 --> 00:00:44,300
CodeCommit happens in your repository, and let's assume that's what happens.

14
00:00:44,300 --> 00:00:47,480
So that CodeCommit from that engineer would then trip off the

15
00:00:47,480 --> 00:00:50,840
build process where you're building the software and you're

16
00:00:50,840 --> 00:00:53,910
running tests against it, etc. etc. etc.

17
00:00:53,910 --> 00:00:57,990
We can incorporate tasks in our Azure DevOps pipelines to

18
00:00:57,990 --> 00:01:00,510
interact with all of the Docker services.

19
00:01:00,510 --> 00:01:05,090
We might in that build process build one or more images and

20
00:01:05,090 --> 00:01:07,940
then push them to Azure Container Registry.

21
00:01:07,940 --> 00:01:09,470
Once that build completes,

22
00:01:09,470 --> 00:01:14,850
we could do a continuous delivery where in a separate release pipeline we

23
00:01:14,850 --> 00:01:17,660
have it set such that when there's a build artifact,

24
00:01:17,660 --> 00:01:19,030
create a new release,

25
00:01:19,030 --> 00:01:24,760
and that new release may then deploy those Azure Container Registry images to,

26
00:01:24,760 --> 00:01:28,070
for example, a managed Kubernetes architecture.

27
00:01:28,070 --> 00:01:29,430
Now this slide is outdated.

28
00:01:29,430 --> 00:01:31,420
It says Azure Container Service.

29
00:01:31,420 --> 00:01:33,900
We would say Azure Kubernetes Service.

30
00:01:33,900 --> 00:01:45,000
ACS was the Microsoft v1 approach at doing enterprise scale containers. Nowadays, we just have AKS, so note that well, all right?