Skip to content

Gateway Patterns

A catalog of things the platform gateway (Envoy Gateway) can do for a service behind it — so you can design against them instead of rebuilding them. Each pattern names the Envoy mechanism, the platform-supported way to ask for it, the security properties, and a live proof.

These sit on top of the identity foundation in Identity & traffic flow — read that first if you haven't; it explains how a verified identity reaches your service as a header.

The catalog

Pattern What it gives you Mechanism
Upstream header injection Attach upstream headers (a credential-reference + custom headers) the client can never set or see — static per-route, or per-user HTTPRouteFilter.credentialInjection, RequestHeaderModifier, SecurityPolicy.extAuth
Identity-scoped routing Restrict a route to certain identities (certain people → certain routes) SecurityPolicy.authorization

How to read a pattern

Every pattern doc has the same shape:

  • What & why — the capability in one paragraph.
  • The flow — which Envoy filter does it, and where in the request path.
  • Platform-supported method — how you ask for it (the manifest shape).
  • Security — what you may assume, and the sharp edges.
  • Proof — a live demonstration (with a GIF).

A note on how these were validated

The patterns were proven on a throwaway experiment against the live gateway. Where a pattern surfaced a real gotcha (e.g. the ext_authz identity-spoofing edge in upstream injection), the doc calls it out — that's the point of a pattern catalog: learn the sharp edges once, here, instead of in production.