A client uses one ordinary ClusterIP Service entry that branches toward eligible Pods. Stable discovery does not guarantee uninterrupted requests.

Kubernetes Services give pods a stable home

A Service separates a stable discovery interface from replaceable backends. The before/after sets are model results, not a transport test. Stable discovery does not prove every request succeeds. Endpoint conditions, ports and datapaths need separate checks. The exact local model passed again; no Kubernetes or transport test was run. One address in front of many An ordinary ClusterIP Service keeps a virtual address during that object’s lifetime, and cluster DNS provides a discovery name. Callers can depend on that name while interchangeable Pods are replaced. This separates a stable client-facing contract from the lifecycle of individual backends, without requiring a config push for every replacement. ...

August 23, 2027 · 6 min · XB Field Notes
A short login-session band ends at logout, while a long user-manager band continues beyond the same boundary with linger enabled.

Linger extends a systemd user manager beyond login

Linger changes when an account’s systemd user manager is kept available. With lingering enabled, logind can start that manager at boot and retain it after the account’s login sessions end. This supports unattended work owned by a normal account. The flag controls manager lifetime; individual services still have their own activation, failure, shutdown, and installation rules. ...

April 20, 2027 · 5 min · XB Field Notes