Welcome back. In this episode, we're gonna discuss a new topic called Containers.
The objectives include understanding what containers are and then understanding some of the technology surrounding them, particularly how they relate to Azure.
So to start, what are containers? Containers are a pretty popular topic right now, and for the rest. This episode we're just gonna cover some introductory concepts and how they integrate with Azure.
First, a container is a software package that contains application code, its dependencies, libraries and other supporting binaries all put together. This allows for deploying the application to different environments much easier as everything the application needs is already part of the container image.
This could be useful if the development and production environments are not identical.
You're basically abstracting away the application from the underlying operating system and the infrastructure that it runs on.
You can have multiple containerized applications, share the same operating system and run in isolation from one another.
The idea of containers is similar to virtual machines running on Veum wear or hyper V. With virtualized servers, you have an entire server packaged up, including the operating system, and it can be moved from host to host containers are very similar to that, except you're not including the underlying operating system.
You're only packaging together the application in its dependencies. This makes the containerized application more lightweight than the entire virtual machine,
so let's talk about some related technologies as they pertain to containers. First is kubernetes. Kubernetes allows for deploying and managing your containerized application. It can provision upgrade and scale. Your resource is on demand without taking them off line.
Kubernetes itself is open source software and originally developed by Google. But now it's maintained by the Cloud Native Computing Foundation and available inside of Azure is the Azure Kubernetes Service, or a K A s. A. K s is a hosted community service that handles task like health monitoring and maintenance.
While you the admin just managed the agent nodes inside your cluster.
Another term you might hear when talking about containers is doctor. So what is Dr
It's a company, and basically they offer a commercialized version of containers they provide at packaging and cluster management, and they use their own orchestration tool called doctors warm. Now, containers and things like kubernetes are open source, but doctor has taken and package it together to make it easier to use for enterprises.
You could think of Docker two containers what maybe Red Hat has done with clinics. They have their own version and offer support and other tools around it.
Finally, another term you might hear is container registry. This is just a repositories of docker container images that you've created for your applications.
The registry is a place for storage as well as distribution of these images.
Doctor does have a public registry available, and Microsoft has its own version with the Azure Container Registry, which is a manage private registry service based on Dr Theat, your containers can be used in your development and deployment pipelines. Azure is container Registry has enterprise grade features like encryption at rest,
and it uses geo, redundant storage and replication
to ensure high availability of your images.
Let's just a couple of basics about containers. What we're going to do in this upcoming episode is create a docker image uploaded to our azure container registry that we're going to make and use it to deploy a Web application.
See you in the next episode