Why Deploying workloads to AKS in Azure? - Purpose & Use Cases

The Big Idea

What if you could deploy your app everywhere with just one command and never worry about servers again?

The Scenario

Imagine you have a website and want to run it on many computers to handle lots of visitors. You try setting up each computer by hand, installing software, copying files, and starting the site. It takes hours or days, and you must repeat this every time you update your site.

The Problem

Doing this by hand is slow and tiring. You might forget a step or make a mistake, causing your site to break. If traffic suddenly grows, you can't quickly add more computers. Managing many machines manually is confusing and risky.

The Solution

Deploying workloads to AKS (Azure Kubernetes Service) lets you tell the system what you want, and it handles the rest automatically. It starts the right number of computers, keeps your site running smoothly, and updates it safely without downtime.

Before vs After

✗ Before

ssh to each server
install software
copy files
start service

✓ After

kubectl apply -f deployment.yaml
kubectl rollout status deployment/myapp

What It Enables

You can quickly and reliably run your applications at any scale without worrying about the details of each machine.

Real Life Example

A company launches a new app and expects many users. Using AKS, they deploy the app once, and it automatically runs on many servers, adjusting as users join or leave, keeping the app fast and available.

Key Takeaways

Manual setup is slow, error-prone, and hard to scale.

AKS automates deployment and management of applications.

This makes running apps easier, faster, and more reliable.

Practice

1. What is the main purpose of using a Deployment in Azure Kubernetes Service (AKS)?

easy

A. To monitor the health of the AKS cluster nodes

B. To manage and maintain a specified number of app copies running

C. To expose the app to the internet

D. To store data persistently for the app

Solution

1. Step 1: Understand Deployment role in AKS

   A Deployment ensures that a specified number of replicas of an app are running and manages updates to those replicas.

2. Step 2: Differentiate from other components

   Persistent storage is handled by volumes, exposure by Services, and monitoring by Azure Monitor, not Deployments.

3. Final Answer:

   To manage and maintain a specified number of app copies running -> Option B

4. Quick Check:

   Deployment manages app replicas = A [OK]

Hint: Deployments keep app copies running smoothly [OK]

Common Mistakes:

• Confusing Deployment with Service for exposure
• Thinking Deployment stores data
• Assuming Deployment monitors nodes

2. Which kubectl command correctly applies a YAML file named app-deployment.yaml to deploy an app to AKS?

easy

A. kubectl create app-deployment.yaml

B. kubectl run app-deployment.yaml

C. kubectl apply -f app-deployment.yaml

D. kubectl deploy app-deployment.yaml

Solution

1. Step 1: Identify correct kubectl syntax for applying YAML

   The command to apply a YAML file is kubectl apply -f filename.yaml.

2. Step 2: Check other options for correctness

   kubectl create requires resource type, kubectl run is for quick pod creation, and kubectl deploy is not a valid command.

3. Final Answer:

   kubectl apply -f app-deployment.yaml -> Option C

4. Quick Check:

   Apply YAML file = kubectl apply -f [OK]

Hint: Use 'kubectl apply -f' to deploy YAML files [OK]

Common Mistakes:

• Using 'kubectl create' without resource type
• Trying 'kubectl deploy' which doesn't exist
• Confusing 'kubectl run' with applying YAML

3. Given this YAML snippet for an AKS Deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 3
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp-container
        image: nginx:latest
        ports:
        - containerPort: 80

How many pods will AKS try to run for this Deployment?

medium

A. 3

B. 2

C. 1

D. 0

Solution

1. Step 1: Identify the replicas count in the YAML

   The replicas field is set to 3, meaning AKS will run 3 pods.

2. Step 2: Confirm no other fields override replicas

   There is no override or scaling specified, so the number remains 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   replicas: 3 means 3 pods [OK]

Hint: Check 'replicas' field for pod count [OK]

Common Mistakes:

• Ignoring the replicas field
• Confusing selector labels with pod count
• Assuming default pod count is 1

4. You applied a Deployment YAML but your pods are stuck in 'Pending' state. Which of these is the most likely cause?

medium

A. The container image name is misspelled

B. The Service type is set to ClusterIP

C. The Deployment YAML is missing the 'replicas' field

D. There are not enough cluster resources to schedule pods

Solution

1. Step 1: Understand what 'Pending' pod state means

   Pods in 'Pending' usually wait for resources like CPU or memory to be available on nodes.

2. Step 2: Evaluate options for causing Pending state

   Misspelled image causes ImagePull errors, missing replicas defaults to 1, and Service type doesn't affect pod scheduling.

3. Final Answer:

   There are not enough cluster resources to schedule pods -> Option D

4. Quick Check:

   Pending pods = resource shortage [OK]

Hint: Pending pods often mean no resources available [OK]

Common Mistakes:

• Confusing image pull errors with Pending state
• Thinking missing replicas stops pod creation
• Assuming Service type affects pod scheduling

5. You want to expose your AKS Deployment to the internet with a stable IP and load balancing. Which Kubernetes Service type should you use in your YAML?

hard

A. LoadBalancer

B. NodePort

C. ClusterIP

D. ExternalName

Solution

1. Step 1: Identify Service types and their purposes

   ClusterIP exposes service inside cluster only, NodePort exposes on node ports, LoadBalancer creates cloud load balancer with stable IP, ExternalName maps to external DNS.

2. Step 2: Choose Service type for internet exposure with stable IP

   LoadBalancer is the correct choice to get a cloud-managed IP and load balancing for external access.

3. Final Answer:

   LoadBalancer -> Option A

4. Quick Check:

   Internet exposure with stable IP = LoadBalancer [OK]

Hint: Use LoadBalancer Service for external stable IP [OK]

Common Mistakes:

• Using ClusterIP which is internal only
• Choosing NodePort which uses random ports
• Confusing ExternalName with load balancing