Managing Deployments, Services, and Pods Tutorial


Managing deployments, services, and pods is an essential aspect of working with Azure Kubernetes Service (AKS). Deployments define the desired state of your applications, services enable communication between components, and pods are the fundamental units that run your containers. In this tutorial, you will learn how to effectively manage these key components in AKS.

Managing Deployments

Deployments in AKS are used to define and manage the lifecycle of applications running in your cluster. To create a deployment, you can use a YAML manifest file that describes the desired state of your application. Here's an example of a Deployment manifest:

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

Once you have the manifest file ready, you can create the deployment using the following command:

kubectl apply -f deployment.yaml

Managing Services

Services in AKS enable communication between different components of your application. They provide a stable IP address and DNS name for accessing your application. To create a service, you can use a YAML manifest file similar to the one below:

apiVersion: v1 kind: Service metadata: name: my-app-service spec: selector: app: my-app ports: - protocol: TCP port: 80 targetPort: 80 type: LoadBalancer

Apply the service manifest using the following command:

kubectl apply -f service.yaml

Managing Pods

Pods are the smallest deployable units in AKS and represent a single instance of a running process. They encapsulate one or more containers that work together. Pods are automatically created by the deployment controller based on the desired state defined in the deployment manifest. You can view the pods in your cluster using the following command:

kubectl get pods

Common Mistakes to Avoid

  • Not properly defining the desired state in the deployment manifest.
  • Using incorrect selectors or labels, which can lead to resource association issues.
  • Not considering resource constraints and not specifying resource requests and limits for pods.
  • Not exposing the necessary ports in the service manifest, resulting in connectivity problems.

Frequently Asked Questions (FAQs)

  1. What is the purpose of a deployment in AKS?

    Deployments in AKS define the desired state of your applications and manage their lifecycle, including scaling and rolling updates.

  2. What is the role of a service in AKS?

    Services in AKS provide a stable network endpoint to access your application and enable communication between different components.

  3. How are pods different from containers?

    Pods represent one or more containers running together on a single node. They provide a shared network namespace and shared storage volumes.

  4. Can I scale my deployment in AKS?

    Yes, you can scale your deployment by adjusting the replica count in the deployment manifest and applying the changes with kubectl.

  5. How can I delete a deployment or service?

    You can delete a deployment or service using the `kubectl delete` command followed by the appropriate resource name.


Managing deployments, services, and pods is crucial for effectively working with Azure Kubernetes Service (AKS). By creating deployments to define the desired state of your applications, managing services to enable communication, and interacting with pods as the running instances, you can efficiently deploy and manage your applications in AKS. Avoid common mistakes such as improperly defining the desired state, using incorrect selectors or labels, and neglecting resource constraints. With these management practices in place, you can successfully deploy and operate your applications in AKS.