docs: branded data-plane error pages enhancement proposal#204
Merged
Conversation
Product-focused proposal to restore the branded HTML error page on the downstream/Connector data plane. The page was delivered via an EnvoyPatchPolicy (local-reply-5xx) that went inert when enableEnvoyPatchPolicy=false was set during the extension-server migration, so customer outages (e.g. offline Connector) now render raw Envoy bodies like "no healthy upstream" instead of the branded page. Proposes delivering the page through the extension server's per-listener mutation (the supported path now that EnvoyPatchPolicy is disabled there), sourcing content from a mounted ConfigMap with a compiled-in fallback so content edits are a GitOps change and a missing/bad page can never block the fail-closed data plane. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Remove the (incorrect) 'inert for months' claim; how long EnvoyPatchPolicy has been disabled is unknown and not relevant to the proposal. - Consolidate content: Risks table now indexes the detailed design sections instead of restating them; Proposal intro defers mechanics to Design Details. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Lead with the functionality the branded data-plane error page provides rather than the migration history. Drop the regression narrative and the EnvoyPatchPolicy-comparison framing; describe the extension-server delivery as the design, not a restoration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Motivation content reads directly under the section header. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mattdjenkinson
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a product-focused enhancement proposal: Branded Data-Plane Error Pages (
docs/enhancements/branded-error-pages/README.md).Why
When a visitor reaches a customer's site through Datum's edge and something goes wrong — the Connector tunnel is offline, the origin is down, a request times out — the response is generated by Envoy, not the customer's app. On the downstream / Connector data plane that response is a raw, unstyled error (e.g.
503 no healthy upstream).That edge error is a trust and brand surface: it's the page a customer's own end-users see during the customer's outage. This proposal delivers a Datum-branded HTML error page for those edge-generated 5xx responses.
Proposal (summary)
Doc follows the existing
docs/enhancements/KEP-style format and is markedstatus: provisional / stage: alpha. Companion to the Envoy Gateway Extension Server proposal.🤖 Generated with Claude Code