Learn from production

• Taming the Storm: Building Groww’s Internal Chaos Engineering Platform

  Groww Engineering Team

  This case study explains how Groww built an internal chaos engineering platform on Kubernetes to run controlled failure drills like network faults, dependency outages, and traffic replay before real incidents hit production.

• Investigating and fixing "stoppodsandbox from runtime service failed" kubelet errors

  In this blog post, the author tracks down persistent sandbox-cleanup errors in a Kubernetes cluster, finds that zero-length CNI cache files cause the problem, and shows how manually deleting those files cleared the error.

• Migrating legacy PHP monolith apps on Drupal 8 to Kubernetes

  Alexey Demyanov

  This case study shows how Palark migrated high-traffic Drupal 8 monoliths to Kubernetes to improve resilience, autoscaling, deployment automation, and DDoS handling while reducing infrastructure waste.

• How we found 7 TiB of memory just sitting around

  This blog post tells how the Render team:

  • tracked down Kubernetes memory waste caused by many daemonset namespace watches,
  • fixed config issues,
  • and freed over 7 TiB of memory across clusters by reducing unnecessary listwatch overhead.

More case studies →

Matching jobs

1. • DevOps Engineer with Miratech

   • Salary: $81K to $297K a year

   • Location: remote from

   • Tech stack: Kubernetes, AWS, ArgoCD, Flux, Docker, Python, Cloudformation, Terraform, GitHub Actions, Jenkins

2. • Engineering Manager with FIRY

   • Salary: $259K a year

   • Location: based in the office (and remote from home) in San Francisco, CA, USA

   • Tech stack: Kubernetes, AWS, Docker, Go, Java, Javascript, Python, Ruby

3. • Head of Site Reliability Engineering with FIRY

   • Salary: $58.5K to $3.29L a year

   • Location: based in the office (and remote from home) in Bengaluru, IN

   • Tech stack: Kubernetes, AWS, ArgoCD, Go, Java, Python, GitHub Actions, Datadog, Prometheus, Jaeger

4. • Head of Site Reliability Engineering with Kontakt.io

   • Salary: $196.2K to $357.5K a year

   • Location: based in the office in New York, NY, USA

   • Tech stack: Kubernetes, AWS, Docker, Terraform, Datadog, Grafana, Prometheus

5. • Platform Engineer with Inversion

   • Salary: $139K to $201K a year

   • Location: based in the office in Playa Vista, CA, USA

   • Tech stack: Kubernetes, AWS, GCP, Docker, Python, Shell, Terraform, GitHub Actions, Jenkins, Grafana

Discover more Kubernetes jobs on Kube Careers →

Build something

• Automating Penetration Testing with SecureCodeBox on Kubernetes, Kind Clusters Using GitHub Actions

  Gyasmine

  This tutorial shows how to run OWASP ZAP scans inside GitHub Actions using SecureCodeBox on a Kubernetes kind cluster.

• Exposing Kubernetes: Dual HAProxy Setup on Proxmox & Ingress Controller

  Vitalii Ruzhnikov

  This tutorial shows how to expose a self-hosted Kubernetes cluster on Proxmox using a dual HAProxy setup one on the host as an edge gateway and one as an in-cluster ingress controller.

• Securing Kubernetes Microservices with Istio: mTLS, Gateways, and the Kubernetes Gateway API

  Matthieu Vlad

  This guide walks through deploying Istio via Terraform and Helm to secure service-to-service and external communication with mTLS, automatic sidecar injection, and encrypted ingress via Istio Gateway.

• Deploy production generative AI at the edge using Amazon EKS Hybrid Nodes with NVIDIA DGX

  Sheng Chen is a Sr. Specialist Solutions Architect at AWS Australia, bringing over 20 years of experience in IT infrastructure, cloud architecture, and multi-cloud networking. In his current role, Sheng helps customers accelerate cloud migrations and infrastructure modernization by leveraging cloud-native technologies. He specializes in Amazon EKS, AWS hybrid cloud services, platform engineering and AI infrastructure.

  This tutorial shows how to run production generative AI at the edge by attaching on-prem NVIDIA DGX systems to an Amazon EKS control plane with hybrid nodes, GPU Operator, and NVIDIA NIM.

More tutorials →

Call for Papers closing soon

1. 0

   days

   Devopsdays Vilnius

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

   • Location: Vilnius, LT

   • In-person conference organized by Devopsdays.

   • The conference starts on the 30 September 2026.

   • Apply here

2. 1

   days

   Texas Linux Fest

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

   • Location: Austin, TX, USA

   • In-person conference organized by TXLF.

   • The conference starts on the 7 November 2026.

   • Apply here

3. 6

   days

   Kubernetes Community Days São Paulo 2026

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

   • Location: São Paulo, BR

   • In-person conference organized by KCD Brasil.

   • The conference starts on the 26 September 2026.

   • Apply here

4. 14

   days

   Kubernetes Community Days Gujarat 2026

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

   • Location: Ahmedabad, IN

   • In-person conference organized by KCD Gujarat.

   • The conference starts on the 19 September 2026.

   • Apply here

5. 16

   days

   Kubernetes Community Days Porto 2026

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

   • Location: Porto, PT

   • In-person conference organized by KCD Porto.

   • The conference starts on the 20 November 2026.

   • Apply here

6. 17

   days

   Subsurface 2026 — The Open Data and AI Conference

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

   • This is a virtual event

   • Online conference organized by Dremio.

   • The conference starts on the 2 October 2026.

   • Apply here

7. 17

   days

   Devopsdays Cairo

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

   • Location: Cairo, EG

   • In-person conference organized by Devopsdays.

   • The conference starts on the 26 September 2026.

   • Apply here

More articles

• Kubernetes security fundamentals: networking

  Rory McCune

  This article covers network security fundamentals in Kubernetes, explaining how clusters default to a flat pod network, how network policies enforce segmentation, and best practices like “default deny” and restricting host networking.

• Using Role-based Access Control in Kubernetes Engine - GSP493

  David Nguyen

  This article shows how to configure Role-Based Access Control (RBAC) in Kubernetes Engine (GKE), create roles, role bindings, and enforce least privilege across namespaces and cluster APIs.

• Conditions, Phases, and Declarative Phase Rules in Kubernetes Operators

  Debdut Chakraborty

  This article explains:

  • why Kubernetes operator status conditions should be the single source of truth,
  • how phase should be derived from conditions via declarative rules,
  • and introduces a Go library for doing this with an interactive browser demo.
• The Missing Layers in Your Kubernetes Operator

  Ægir Máni Hauksson

  This article explains that Kubernetes operators become hard to maintain without explicit component and resource-primitive layers between the controller and raw objects.

Even more articles →