Skip to content

Convergence Reliability Work #295

Description

@ecv

Why this exists

This tracks our convergence-reliability work: making an HTTPProxy stand up quickly and reliably, and keeping one tenant or one control plane from dragging the whole fleet. Open issues are ranked by likely impact so we work the highest-leverage fixes first, not the freshest.

The lens comes from the recent per-stage investigation (https://github.com/datum-cloud/infra/issues/3622): the cost of standing up an HTTPProxy is queue serialization, requeue floors, and DNS-agent saturation — not compute. Ranking favors blast radius, user-facing breakage, and fixes we already have evidence for.

Fleet-wide / all-tenant blast radius

User-facing feature broken

Convergence latency (current theme, actionable now)

Observability / prevention

Lower / longer-horizon

Design-scale:

Docs / e2e:

Dashboards / status plumbing:

GatewayClass hygiene:

Networking / deps:

Misc:

Recommended next, best impact × actionable × rides current momentum

  1. Custom-hostname DNSRecordProgrammed stuck Pending >60s on fresh zone (breaches convergence SLO) #291 + Gateway *.datumproxy.net address resolves in 65–85s, exceeding the 60s convergence SLO #292 — DNS-agent queue; metrics in hand, one fix, direct convergence win (dns-operator + infra overlay).
  2. OIDC SecurityPolicy with a missing clientSecret takes down the entire shared downstream gateway (EG v1.8.x); needs e2e reproduction #194 — all-tenant outage; guard + e2e upgrade-gate.
  3. Generalize reconcile-error-ratio alerts to all controllers #289 — telemetry, so the fixes above are verifiable.

Context

Convergence investigation and per-stage attribution: https://github.com/datum-cloud/infra/issues/3622.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

Priority

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions