Zero-Downtime Microservice Deployments with Kubernetes, Docker & GitHub Actions

1. Native Kubernetes Rolling Updates

Rather than replacing all running instances simultaneously (which causes site-wide outages), Kubernetes natively supports rolling updates. This strategy gradually replaces old Pods with new ones, ensuring a minimum number of healthy instances are always available to serve incoming traffic.

• Ensures zero downtime by maintaining a specified percentage of running pods during the update (e.g., maxUnavailable: 0).
• Automatically pauses the rollout if the new container crashes or fails its readiness probes.
• Eliminates the need for complex external traffic routing tools by utilizing the native kube-proxy.

2. Automating Deployments with GitHub Actions

To remove human error from the equation, we automate the rollout using GitHub Actions. Upon a merge to the main branch, the workflow builds the new Docker image, tags it uniquely with the commit SHA, pushes it to the registry, and commands the Kubernetes cluster to update the deployment.

name: Production Deployment

on:
  push:
    branches: [ "main" ]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v4

      - name: Build and Push Docker Image
        run: |
          docker build -t my-registry/backend-api:${{ github.sha }} .
          docker push my-registry/backend-api:${{ github.sha }}

      - name: Set Kubernetes Context
        uses: azure/k8s-set-context@v3
        with:
          kubeconfig: ${{ secrets.KUBECONFIG }}

      - name: Trigger Rolling Update
        run: |
          # Update the deployment with the new image tag
          kubectl set image deployment/api-service api-service=my-registry/backend-api:${{ github.sha }}
          
          # Wait for the rolling update to complete successfully
          kubectl rollout status deployment/api-service --timeout=90s