Azure Container and Resource Management

Azure Container Instances (ACI) is a service for running isolated containers in Azure. It's a good choice for simple applications, task automation, and build jobs. For more complex needs like service discovery, automatic scaling, and coordinated upgrades, Azure Kubernetes Service (AKS) is recommended.

Azure Container Apps is a serverless platform that allows you to run containerized applications with minimal infrastructure management. It offers advantages like cost efficiency and reduced maintenance.

Bicep is a domain-specific language (DSL) for deploying Azure resources declaratively. It simplifies the creation and management of infrastructure as code (IaC) compared to Azure Resource Manager (ARM) templates.

An AKS cluster consists of two components: The control plane, managed by Azure, and worker nodes (virtual machines).

A node pool is a group of identical virtual machines within an AKS cluster, providing a dedicated and isolated environment for your deployments. You can create multiple node pools for different environments, like development and production.

A pod is a fundamental unit of deployment in Kubernetes. It represents a group of one or more containers that share resources and network. Typically, a pod has a 1:1 mapping with a container, but you can run multiple containers within a single pod.

You can deploy Docker images to both Azure Web Apps and Azure Functions Apps.

The API server exposes the Kubernetes API, allowing requests to the cluster from within and outside.

etcd is a highly available key-value store that manages the state and configuration of your Kubernetes cluster.

The scheduler is responsible for deciding where pods should run, choosing the best node based on various factors.

The controller manager runs various control processes to monitor the cluster's health and respond to events, such as node failures.

The cloud controller manager runs specialized controllers for cloud providers, managing resources like load balancers.

kubelet is a service running on each worker node responsible for ensuring containers are running within pods.

kube-proxy handles network rules on each node, ensuring pods can communicate with each other and the outside world.

The container runtime manages the lifecycle and execution of containers, controlling how they start, stop, and interact.

A Kubernetes object that ensures a specific number of pod replicas are running at any time, even in the event of failure. It automatically creates a new pod to replace a failed one.

A Kubernetes controller that ensures a specific pod runs on all nodes (or a specific subset of nodes) in a cluster. It automatically schedules pods on new nodes.

A type of Kubernetes Service that exposes a service on a specific cluster IP address. It is only accessible within the cluster.

A Kubernetes Service that exposes applications on a specific node port. It allows access from outside the cluster.

A Kubernetes service that provides external access to your application. It assigns a public IP address to the service.

A Kubernetes object used to store sensitive information, such as passwords or API keys. It keeps this information secure.

A Kubernetes object used to store configuration data for applications, like database connection strings or API endpoints. It makes it easy to manage configuration across multiple environments.

A Kubernetes object that provides a logical grouping for resources. It helps to organize and manage resources within a cluster.

A command-line tool used to interact with Kubernetes clusters. It allows you to create, manage, and monitor Kubernetes resources.

A command used to launch a new pod in Kubernetes. It takes an image as input and creates a pod based on that image.

A Kubernetes component that configures iptables rules on each node to forward traffic to pods. It ensures that pods, which are ephemeral, can be reached by external services.

A component that acts as an IP masquerading agent, handling outgoing traffic from pods to external destinations. It can be configured to exclude specific IP ranges, allowing traffic within those ranges to retain its original pod IPs.

A standard for providing storage services to containerized applications. It simplifies integrating storage with Kubernetes by allowing plugins to be developed and deployed independently.

This Azure resource group, encompassing the Azure resources used in your AKS cluster, should be customized using AKS node pools. Avoid directly modifying its resources, as it can disrupt cluster functionality.

A DNS service for Kubernetes clusters, offering name resolution for services within the cluster.

A component responsible for establishing network connections between the API server and worker nodes. It handles essential tasks like health checks and managing pod and node status.

A mechanism for distributing traffic from pods to nodes. It ensures traffic is routed efficiently based on rules and configurations.