Skip to content
datastudyguides

AI-200 · 1.2.3 · Develop containerized solutions on Azure

AKS manifests

Deploy and manage applications to Azure Kubernetes Service (AKS) by using manifest files

A Deployment runs and a Service exposes them. Their labels and ports must line up for traffic to reach the app.

Deployment plus Service

AKS manifest infographic showing a Deployment that creates pods and a Service that exposes them, with the Service selector matching pod labels.

A Deployment owns the . A Service gives matching pods a stable endpoint. The Service selector must match pod labels, and targetPort must match the port where the container listens.

Put runtime needs in the manifest

spec:
  template:
    metadata:
      labels:
        app: orders-api
    spec:
      containers:
      - name: api
        image: shopreg.azurecr.io/shop/orders-api:b4821
        resources:
          requests:
            cpu: 200m

Resource requests help Kubernetes schedule pods. A CPU-based HorizontalPodAutoscaler also needs CPU requests because utilization is calculated against the requested CPU.

Apply and inspect

az aks get-credentials --resource-group rg-shop --name aks-shop
kubectl apply -f orders.yaml
kubectl rollout status deployment/orders-api
kubectl get service orders-api

Use ClusterIP for an internal endpoint and LoadBalancer when Azure should provision an external endpoint.

Pull private images

Attach to so the cluster identity gets pull permission. This avoids storing registry credentials in the manifest.

Key points

  • Apply: ` apply -f` creates or updates declared objects
  • Service wiring: selector matches labels; targetPort matches container port
  • Resources: CPU and memory requests guide scheduling
  • HPA: CPU utilization scaling needs CPU requests on the containers
  • Service type: ClusterIP internal, LoadBalancer external
  • Private : attach the registry so the cluster identity can pull

Click an underlined term for a one-line explanation, or see them all in the glossary .

Exam trap

If cannot pull a private image whose name is correct, the cluster lacks permission on the registry; attach the registry.

Sources · 3 Microsoft Learn pages Show ▾

Checked on October 4, 2026. Report a problem

Go deeper on Microsoft Learn

Checked against Microsoft Learn on October 4, 2026. Report a problem with this card

How well do you know this?