Steve Kriss

_Posted by @viju2008 on #4450:_ > **Please describe the problem you have** [A clear, concise, description of the problem you are facing. What is the _problem_ that feature X would...

@echupriyanov I believe that per https://github.com/projectcontour/contour/issues/3692#issuecomment-845351552, as a workaround right now if you set the route's [response timeout](https://projectcontour.io/docs/v1.15.1/config/api/#projectcontour.io/v1.TimeoutPolicy) to something larger than `15s`, that will effectively be the stream timeout...

I don't think I worked on this feature, but I'll take a look and see if I have anything to add.

One idea I had was that we could use something like the Deployment -> ReplicaSet model -- each time the Deployment's spec changes, a new ReplicaSet is created, that's owned...

xref #3071 #3039

> I'm currently a -1 on the idea of having an intermediate resource representing the configuration, mainly because it feels to me like too much indirection. I agree that's how...

Couple thoughts: - I'd switch the version numbers to v0.2.0, v0.3.0, etc. since they'll be more than bug-fix releases (ref. https://semver.org/) - Getting to passing Gateway API conformance is (a)...

> this is one of those changes where we have a conflict between `main` of Contour + the latest GW API conformance release Yeah, I guess this brings up a...

cc @sunjayBhatia, I'm thinking it'd be nice to have a sample gRPC client & server that folks could actually run as part of the guide -- could containerize the demo...

> also to accompany maybe some e2e tests to make sure we can show everything works Big :+1: