Stable address

As explained in Kubernetes in Action, Second Edition

A stable address is a network address that remains associated with a workload identity when its underlying pod is replaced or relocated.

A stable address remains associated with a workload identity when its underlying pod is replaced or relocated. Distributed systems such as MongoDB replica sets need this identity so replicas and clients can reconnect reliably. section 16.1.1

A stateful replica deployment requires:

• A separate PersistentVolume for each pod. section 16.1.1
• A unique address for every pod. section 16.1.1
• The same address and PersistentVolume after pod deletion and replacement. section 16.1.1

Per-replica services

Associate each replica with its own Deployment, Service, and PersistentVolumeClaim. The Service provides an address that continues resolving to the replica's pod when Kubernetes recreates that pod elsewhere. A separate client-facing Service can expose all replicas through one address. section 16.1.1

Figure 16.2 Providing each replica with its own volume and address

View the architecture connecting each replica to its own volume and stable address. section 16.1.1

How Kubernetes in Action, Second Edition covers it

How deep it goes

Explains address continuity through per-replica Services and pod replacement, but does not detail controller internals.

Examples

Uses MongoDB replicas, per-replica Services, and an architecture diagram pairing each replica with its own volume and address.

What it assumes

Assumes familiarity with pods and persistent storage while establishing why distributed replicas need individual identities.

What you can do after

Build it from scratch by pairing each replica with a Deployment, Service, and PersistentVolumeClaim.

How it connects

Connects stable addresses with MongoDB replica sets, Services, Deployments, PersistentVolumeClaims, and PersistentVolumes.

liveBookmanning.com

Read Kubernetes in Action, Second Edition on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.