Expand description
Service mesh config schema (DW-107).
The top-level mesh block configures service mesh mode: dwara runs
as a sidecar in each pod, intercepting traffic via iptables/TPROXY
redirect, with mTLS identity provided by SPIFFE/SPIRE (X.509 SVIDs).
The schema is always present so configs round-trip; the mesh runtime
is scaffolded and Enterprise-only: validation warns when mesh is
configured without the ent feature (or when the scaffolded
runtime is not wired).
See the mesh domain module for the sidecar
controller and SPIFFE client scaffolds.
Structs§
- Mesh
Config - Top-level service mesh config (DW-107,
gateway.mesh). - Mesh
Sidecar Config - Sidecar listener and redirect config (DW-107,
gateway.mesh.sidecar). - Mesh
Spiffe Config - SPIFFE/SPIRE identity config (DW-107,
gateway.mesh.spiffe).
Enums§
- Mesh
Mode - The service mesh mode. v1 ships
sidecar(dwara runs as a sidecar in each pod). Future modes (node-level, CNI-based) are deferred; validation rejects any value other thansidecar.