Learn from production

• Kafka on Kubernetes: Performance Lessons for Any Disk-Heavy Data Service

  Jacob Amar

  This case study traces why Kafka started reading from disk after moving from EC2 to EKS, and lands on cgroup v2 reclaim pressure.

• When ETCD Crashes, Check Your Disks First: A Pod CrashLoopBack Debugging Story

  Anastassios Nanos

  This case study shows how etcd CrashLoopBack pods on a Karmada/k3s demo cluster turned out to be a ZFS I/O latency problem, and how four ZFS tuning settings fixed it — including the exact etcd Prometheus metrics to watch.

• Zero-Downtime EKS Migration: Production-Grade Kubernetes at Scale

  Krishnakanth E

  This case study explains how an ECS workload was migrated to EKS across two AWS regions with zero production downtime.

  It covers KEDA autoscaling, HashiCorp Vault, IRSA, disaster recovery, and a coordinated production cutover.

More case studies →

Matching jobs

1. • DevOps Engineer with Mark43

   • Salary: $155K to $170K a year

   • Location: remote from

   • Tech stack: Kubernetes, Docker, Terraform

2. • DevOps Engineer with RobCo

   • Salary: US$70.74K to US$440K a year

   • Location: based in the office in Munich, DE

   • Tech stack: Kubernetes, AWS, Go, Python, Terraform, Datadog, Grafana, Prometheus

3. • Site Reliability Engineer with MyFitnessPal

   • Salary: $120K to $165K a year

   • Location: remote from

   • Tech stack: Kubernetes, AWS, Docker, Go, Python, Typescript, Terraform, GitHub Actions, Datadog

4. • AI Enterprise Technical Program Manager with Redhorse Corporation

   • Salary: $37 to $485.65K a year

   • Location: based in the office in Arlington, VA, USA

   • Tech stack: Kubernetes, AWS, Azure, Docker, Spark

5. • Commercial Account Executive with Vantage

   • Salary: $100K to $200K a year

   • Location: remote from

   • Tech stack: Kubernetes, AWS, CircleCI, Datadog

Discover more Kubernetes jobs on Kube Careers →

Build something

• Deploying WSO2 API Platform Gateway on OpenShift: A Practical Guide

  Osura Viduranga

  This tutorial walks through deploying the WSO2 API Platform Gateway on OpenShift, from building the images and installing cert-manager to applying the gateway operator, a sample REST API, and the route that exposes it.

• From Ingress to Gateway API: How We Modernized Networking on Our GKE Cluster

  Dharmendra Yadav

  This tutorial explains why Gateway API replaces Ingress on GKE, walking through GatewayClass, Gateway, and HTTPRoute, then sets up traffic splitting and TLS without vendor-specific annotations.

• Building a Real k6 Test Suite Against a Live Kubernetes App

  Matthew Wimpelberg

  This tutorial builds a real k6 test suite against Google's Online Boutique running on a home lab Kubernetes cluster, with a shared client library, smoke, load, stress, and browser tests, and the two bugs the first run exposed.

• Autoscalable GitLab runners on AWS EC2

  Timur Nizamutdinov

  This tutorial shows how to replace always-on EC2 runners with autoscaling GitLab runners using the AWS fleeting plugin and an Auto Scaling Group, so instances start per job and shut down when the queue is empty.

More tutorials →

Call for Papers closing soon

1. 1

   days

   Monster Scale Summit 2027

   The Call For Paper is open until 28 August 2026 at GMT-4. More info →

   • This is a virtual event

   • Online conference organized by ScyllaDB.

   • The conference starts on the 11 March 2027.

   • Apply here

2. 1

   days

   Dynatrace Perform 2027

   The Call For Paper is open until 28 August 2026 at GMT-4. More info →

   • Location: Las Vegas, NV, USA

   • In-person conference organized by Dynatrace.

   • The conference starts on the 16 February 2027.

   • Apply here

3. 4

   days

   Devopsdays Warsaw

   The Call For Paper is open until 30 August 2026 at GMT-4. More info →

   • Location: Warsaw, PL

   • In-person conference organized by Devopsdays.

   • The conference starts on the 23 November 2026.

   • Apply here

4. 4

   days

   Devopsdays Recife

   The Call For Paper is open until 30 August 2026 at GMT-4. More info →

   • Location: Recife, BR

   • In-person conference organized by Devopsdays.

   • The conference starts on the 12 December 2026.

   • Apply here

5. 4

   days

   Devopsdays Florianópolis

   The Call For Paper is open until 30 August 2026 at GMT-4. More info →

   • Location: Florianópolis, BR

   • In-person conference organized by Devopsdays.

   • The conference starts on the 24 October 2026.

   • Apply here

6. 4

   days

   OmniOpenCon 2026

   The Call For Paper is open until 31 August 2026 at GMT-4. More info →

   • Location: Bucharest, RO

   • In-person conference organized by OmniOpenCon.

   • The conference starts on the 18 October 2026.

   • Apply here

7. 4

   days

   Devopsdays Boston

   The Call For Paper is open until 31 August 2026 at GMT-4. More info →

   • Location: Boston, MA, USA

   • In-person conference organized by Devopsdays.

   • The conference starts on the 19 October 2026.

   • Apply here

More articles

• Your AI just deleted the wrong deployment. Now what?

  mirusser

  This article argues that MCP servers for Kubernetes ship the accelerator without the brake, and walks through a two-tier design in which an agent can only propose a change, and a human approves the exact plan before it is applied.

• Vlan migration: moving a live Kubernetes cluster without downtime

  zolty

  This case study covers migrating a live k3s cluster from a flat network to a VLAN architecture, including an etcd quorum loss caused by moving too many nodes at once and the recovery steps using k3s server --cluster-reset.

• To Centralise or Not to Centralise: The Questions That Shaped the Kubernetes CODECO Federated Architecture

  Rute C. Sofia

  This article explains the centralise-or-not trade-off behind CODECO's federated Kubernetes architecture across cloud, edge and IoT, and how neighbourhood-scoped control, decentralised AI and federated scheduling answer it.

• The Illusion of CPU: Why HPA Fails for Pub/Sub Consumers and What to Do Instead

  Sujith K. Surendran

  This article explains why CPU is the wrong scaling signal for Pub/Sub consumers, since pods look healthy while the backlog grows, and argues for scaling on queue depth with KEDA instead.

Even more articles →