---
id: w1/m23/t004
title: Sweep stale "single-node / data-loss" comments inverted by the m19 rebuild
worker: worker1
status: todo
estimate: 30m
depends_on: []
---

## Objective

Correct in-tree claims the m19 rebuild made false in bex's favor: hcloud-csi network volumes are now the prod default StorageClass (so Loki/Prometheus history survives node loss), and the private network is CAPH's `bex` `10.10.0.0/16`. Comment/doc-only, zero behavior change.

## Context

- `deploy/gitops/base/loki.yaml`, `prometheus.yaml`, `log-shipper.yaml` — comments still claim local-path/single-node history loss.
- `docs/ADR010-observability.md:42` — same inverted claim.
- `deploy/gitops/base/values/traefik.values.yaml:9-15` — cites the dead `10.0.0.0/16` (now `10.10.0.0/16`).
- `docs/ADR002-architecture.md` §Data layering — "business state lives only in the single app node's etcd" predates the multi-node world (still a single etcd member until the quota revert, but no longer a single-node cluster).

## Steps

1. Update each comment/doc line to the post-m19 reality (network volumes survive node loss; `10.10.0.0/16`).
2. For the ADR002-architecture.md line, distinguish "single etcd member (interim)" from "single-node cluster (false)".
3. `npx prettier@3.4.2 --write "**/*.md"`.

## Files

- `deploy/gitops/base/{loki,prometheus,log-shipper}.yaml`, `deploy/gitops/base/values/traefik.values.yaml`, `docs/ADR010-observability.md`, `docs/ADR002-architecture.md`

## Acceptance criteria

- [ ] No file asserts local-path/single-node history loss or the dead `10.0.0.0/16` network.
- [ ] Zero behavior change (comments/docs only); markdown prettier-clean.

## Out of scope

- Any behavioral change to storage/network config.
