Bootstrap
The Envoy bootstrap config Elchi generates for each proxy — node identity, admin, static resources, and the ADS connection back to the control-plane.
The Envoy bootstrap config Elchi generates for each proxy — node identity, admin, static resources, and the ADS connection back to the control-plane.
How Elchi models Envoy clusters (CDS) — discovery type, load balancing, health checks, circuit breakers, and outlier detection.
Three inspection tools for understanding and debugging Envoy config in Elchi — visualize how resources reference each other, trace request routing, and dump the live xDS snapshot Envoy is actually serving.
How Elchi models Envoy endpoints (EDS) — the ClusterLoadAssignment, localities, priorities, weights, and their link to clusters.
How Elchi surfaces Envoy typed_config extensions — reusable, separately-managed configs referenced by other resources.
How Elchi models Envoy filters — the listener, network, HTTP, and UDP filter categories the UI exposes, and where WAF and ext_proc fit.
How Elchi models Envoy listeners (LDS) — bind addresses, filter chains, the HTTP Connection Manager, and TLS termination.
Trace how an incoming request flows through a listener's virtual hosts, routes, and match conditions to the upstream cluster that ultimately serves it.
How Elchi models Envoy route configurations (RDS) — virtual hosts, match/route/redirect rules, and header manipulation.
How Elchi models Envoy secrets (SDS) — TLS certificates, validation contexts, and the link to ACME-managed certificates.
Inspect the exact xDS snapshot the control-plane is serving a live Envoy node — the ground truth of what shipped — and clear a stale snapshot to force a resync.
Reusable Envoy config building blocks in Elchi — per-type resource templates for consistent starting points, and searchable field-level snippets for repeated fragments, with batch operations.
How Elchi models Envoy transport sockets — downstream vs upstream TLS/mTLS on listeners and clusters, plus QUIC and Proxy Protocol.
How Elchi models Envoy virtual hosts inside a route configuration — domains, per-vhost routes, retries, and header rules.