Kubernetes Reliability at Scale

How to Improve Uptime with Resiliency Management

In this comprehensive guide to building your own resiliency management practice for Kubernetes, you’ll learn:

  • Common Kubernetes reliability risks and how to identify critical risks.
  • How to monitor for critical risks and validate resilience to them.
  • The key processes, standards, and roles needed to ensure resilience across your organization.
  • How to integrate resiliency management smoothly into your existing processes.

Get the eBook

Thanks for requesting the Kubernetes Reliability at Scale: How to Improve Uptime with Resiliency Management. View the guide here. (A copy has also been sent to your email.)

About the Authors

Jordan Pritchard

Director of Infrastructure & Site Reliability Engineering

Michael Kehoe

Architect of reliable, scalable infrastructure

Rodney Lester

Technical Lead, Reliability Pillar of Well Architected Program

Tammy Butow

Principal SRE

Jay Holler

Manager, Site Reliability Engineering

Ramin Keene


There’s more pressure than ever to deliver high-availability Kubernetes systems, but this is easier said than done—especially when the complex, ephemeral nature of Kubernetes makes it harder to detect reliability risks before they cause outages.

The key is to build a Kubernetes resiliency management practice, one that seamlessly integrates with your observability and incident response practices to improve your Kubernetes uptime.

By using the framework and practices in this book, you’ll be able to prevent incidents and outages, accelerate key IT initiatives, and shift-left reliability efforts into your Software Development Lifecycle.

  • Incident classification: SEV descriptions and levels, and SEV and time-to-detection (TTD) timelines

  • Organization-wide critical service monitoring, including key dashboards and KPI metrics emails

  • Service ownership and metrics for organizations maintaining a microservices architecture

  • Effective on-call principles for site reliability engineers, including rotation structure, alert threshold maintenance, and escalation practices

  • Chaos Engineering practices to identify random and unpredictable behavior in your system

  • Monitoring and metrics to detect incidents caused by self-healing systems

  • Creating a high-reliability culture by listening to people in your organization

Over a decade of collective experience unleashing chaos at companies like

Avoid downtime. Use Gremlin to turn failure into resilience.

Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.GET STARTED

Product Hero ImageShape