Migrate IIS Web Apps to Azure Kubernetes Service.
Now, like I warned you at the beginning of this lesson,
the exam is not going to get into the weeds into the
finer points of containerization and AKS,
that's covered under separate certifications.
We don't have the time or the scope.
but absolutely look at the Pluralsight library because
many good friends of mine actually, Anthony Nocentino comes to mind,
have courses on this stuff in the library, and I would trust
anything they have to say on the subject.
Let me give you the Cliff's notes here from a hybrid
cloud administrator's standpoint, alright?
So let's look at step one here.
Your developers want to begin to use these Docker containers to,
instead of building big old monolithic applications that are kind of
difficult to scale and kind of difficult to update and secure,
they want to use Docker tools to create these images that contain
just the application and it's dependencies.
So you might wind up with the three‑tier application with three containers,
one for the database, one for the API, and one for the front end.
You see?
Much more modular way to go,
and the idea when you're using Docker is that we can use the
same tools and images and go to Azure, go to Google,
go to AWS, and go to on‑prem with minimal or no refactoring.
So that's just a nutshell elevator pitch on some of the
benefits of using Docker containers in a microservices
application development context.
Anyway, the developer uses the Docker tools,
including a Docker domain specific language to build out these images.
You've got a plaintext Docker file script that builds or instructs the
Docker build tools how to create this binary deliverable.
This is going to be your application and its dependencies without
all the unnecessary cruft of a virtual machine,
which is the normal alternative to using Docker containers,
alright?
Now that image is the deployable unit,
and we need somewhere for our developers to push or upload those images.
Guess what?
In your Azure subscription,
you have an Azure container registry that gives you
private authenticated access.
You can do digitally signed images,
you can configure vulnerability scanning on those images.
The container registry is a really great product.
Alright.
And then once you're there, you can then run or start containers from that image,
and as you can see, there are a number of services to choose from.
The two that we're concerned with chiefly are app
service and Azure Kubernetes Service.
App service, you might think, wait a minute,
that's what we were just looking at in terms of a code deployment.
Well, as it happens, app service can function with raw code,
but you also can push a container image into it as well.
The issue with that though is that it's not as scalable as
using a full‑fledged cluster orchestrator like Kubernetes
and Azure Kubernetes Service, or AKS, is the native Microsoft Azure hosted implementation of Kubernetes.