Azure 클라우드 — Container-based applications
1. Azure Container-based applications
2. Azure Kubernetes Service
3. The ingress Controller in AKS
4. Azure Batch
1. Azure Container-based applications
Azure Container Registry
An Azure container registry is a private Docker registry in Azure where you can store and manage private Docker container images and related artifacts.
- Basic
- Standard: increased included storage and image throughput
- Premium: geo-replication, private link with private endpoints, content trust for image tag signing
Azure Container Instances(ACI)
Azure Container Instances enables a layered approach to orchestration, providing all of the scheduling and management capabilities required to run a single container, while allowing orchestrator platforms to manage multi-container tasks on top of it.
Because the underlying infrastructure for container instances is managed by Azure, an orchestrator platform does not need to concern itself with finding an appropriate host machine on which to run a single container.
Azure Container Instances can schedule both Windows and Linux containers with the same API. Orchestration of container instances exclusively Because they start quickly and bill by the second, an environment based exclusively on Azure Container Instances offers the fastest way to get started and to deal with highly variable workloads.
→ The front-end tier, The backend tier, Both containers must be able to access the Same Azure file share.
Web App Containers
2. Azure Kubernetes Service
- Support a custom domain name and an associated SSL certificate.
- Scale-out automatically based on demand.
- Minimize administrative effort and costs.
AKS Kubernetes Cluster
- hosting Micro service based applications.
- the container images already have the dependencies pre-installed, so you don’t need to install the dependencies.
3. The ingress Controller in AKS
- Control access to the APIs by using mutual US authentication between API Management and the AKS-based APIs.
- Provide access to the APIs by using a single IP address.
An ingress controller is a piece of software that provides reverse proxy, configurable traffic routing, and TLS termination for Kubernetes services. Kubernetes ingress resources are used to configure the ingress rules and routes for individual Kubernetes services. Using an ingress controller and ingress rules, a single IP address can be used to route traffic to multiple services in a Kubernetes cluster.
Container Access Policy
Data access changes must be minimized.
4. Azure Batch
Azure Batch is a compute management platform from Azure that allows for large-scale parallel batch workloads to be run in the cloud. Azure Batch has made the provisioning of many scalable high-performance resources easy and affordable to end-users.
예제)
Each node must communicate data to every other node.
Maximize the number of nodes to calculate multiple scenes as fast as possible.
- Create a render farm that uses Azure Batch.
- Enable parallel task execution on compute nodes.
예제)
The first job type will consist of short-running tasks for a development environment. → User subscription and low-priority virtual machines. Azure Batch offers low-priority virtual machines (VMs) to reduce the cost of Batch workloads. Low-priority VMs make new types of Batch workloads possible by enabling a large amount of compute power to be used for a very low cost.
The second job type will consist of long-running Message Passing Interface (MPI) applications for a production environment that requires timely job completion. → Batch service and dedicate virtual machines