liveBook · Manning

Zero downtime

As explained in Platform Engineering on Kubernetes

Zero downtime is an operational condition in which a service remains available while software changes are applied.

Zero downtime keeps a service available while software changes are applied. Kubernetes provides resilience and scaling mechanisms that let teams update application components without stopping the entire application. section 2.5

Reliable zero-downtime delivery depends on:

  • Releasing components independently instead of stopping the whole application for each update. section 2.5
  • Automating deployment workflows and avoiding older practices that interrupt releases. section 2.5
  • Defining clear contracts between services so dependent components can be released independently. section 2.5

Updating a Kubernetes application

A Kubernetes cluster runs a cloud-native application whose services are packaged with Helm. Kubernetes resources expressed as YAML describe the application topology, containers, and service configuration, allowing components to be updated while the application remains available. section 2.5

How Platform Engineering on Kubernetes covers it

How deep it goes
Explains the operational rationale and dependencies but defers detailed release strategies to later treatment.
Examples
Uses a Kubernetes cluster, Helm packaging, YAML resources, and independently updated application services.
What you can do after
Operate Kubernetes-based releases that update application components without stopping the entire application.
How it connects
Connects Kubernetes with resilience, scaling, continuous delivery, automation, platform engineering, and service contracts.

Also explained in

Compare how 3 books explain zero downtime →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Platform Engineering on Kubernetes. The section links point to the parts of the book it draws on.