Course contentsShow
← Cloud and Infrastructure
Lesson 2566 of 2,98955. Microservices on CloudFree lesson

Microservices on Kubernetes

Deploying microservices as pods, using services for discovery, and namespace organization.

Microservices on Kubernetes

What you'll learn: How to deploy and organize microservices using Kubernetes pods, services, and namespaces for scalable cloud infrastructure.

The Core Idea

Kubernetes provides the perfect runtime environment for microservices by treating each service as a pod (the smallest deployable unit), enabling service-to-service communication through Services (Kubernetes resources for discovery), and organizing everything logically with namespaces.

Think of Kubernetes as an apartment building: each microservice lives in its own pod (apartment), Services act as the building directory helping residents find each other, and namespaces are different floors that keep teams or environments separated.

Deploying Microservices as Pods

Each microservice runs in one or more pods. A pod wraps your containerized application and can be replicated for scaling:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: user-service
spec:
  replicas: 3
  template:
    spec:
      containers:
      - name: user-service
        image: myregistry/user-service:v1

Service Discovery with Services

Kubernetes Services provide stable endpoints for pod-to-pod communication, handling load balancing automatically:

apiVersion: v1
kind: Service
metadata:
  name: user-service
spec:
  selector:
    app: user-service
  ports:
  - port: 80
    targetPort: 8080

Other microservices can now reach this one at http://user-service.

Namespace Organization

Namespaces isolate microservices by team, environment, or domain:

kubectl create namespace payment-domain
kubectl create namespace user-domain

This keeps your payment services separate from user services, applying different policies and resource limits to each.

Key Takeaway: Kubernetes manages microservices through pods for deployment, Services for discovery and load balancing, and namespaces for logical organization—providing infrastructure that matches your service boundaries naturally.