contour
contour copied to clipboard
Ability to specify custom error page
It'd be nice to have a way to show a custom error message if an error happens at the contour level, such as no healthy upstream servers.
If there is already a way to do this, it'd be nice to document it.
Blocked:
- [ ] https://github.com/envoyproxy/envoy/issues/1178
This sounds like a good thing to have if someone wants to investigate the options inside Envoy for doing this.
Looks like Envoy will support custom error responses in 1.9.0: https://github.com/envoyproxy/envoy/issues/1178.
This is something i’d like to see fo contour 1.0. Marking as 0.15 to review if the feature has landed upstream.
This feature right now is scheduled for Envoy v1.12.0.
Thanks for checking. I'm moving this to the unplanned milestone. It's unlikely that we'll make it to envoy 1.12 by october for contour 1.0 so we'll reassess after contour 1.0 ships.
xref #2515 which is closely related
This will help i think https://github.com/envoyproxy/envoy/pull/11007
Yup, that looks promising.
xref #1898
@jpeach @stevesloka @sgringwe I think we can close this one right ?
@OrlinVasilev nope, you'd need a way to configure this in Contour now. =) It's great envoy has support now, so please leave open to add the Contour support.
Great thanks!! @stevesloka
Hi, just chiming in from what I think was creating a duplicate Issue. Essentially I'm looking for a way to handle a few cases:
- When upstreams are unhealthy, rather than a static 503, I would like to customize the content. This is similar to how some cloud service providers handle things on eg "AWS Application Load Balancers".
- When a wildcard parent route is specified, but the child router is not yet, or invalid, it would be nice to beable to "fall back" to a default handler.
In my days where I'd use the more common NGINX based ingresses, they used a feature called the default backend to accomplish some of these features.