FA-10137 / Deployment models / Member archive

Replica rollout status: Failed replicas do not degrade rollout · case 02

Failed replicas do not degrade rollout.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Report blocked on invalid specification, degraded on failed required replicas, progressing when observed generation lags, progressing when updated or available counts are below desired, otherwise ready. Zero desired is ready when observed.

Why this case matters

An offline model of replica rollout status, suitable for testing build and release tooling without external services.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 2	`"ready"`	`"degraded"`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.