Julian Friedman

@BlueOrigin since you're still mentioned from this interaction even with the original comment edited, you might also want to click "unsubscribe" on the sidebar manually :)

/remove-lifecycle stale

We _may_ want to wait for https://github.com/knative/serving/issues/10851 to land before picking this one up to avoid potentially solving some of the same/similar problems twice (Unless @skonto things they're independent enough...

> Maaaybe something like Rust, ... it does sound kind of fun as a proof of concept. I mean envoy is written in _c++_ and has survived ok so.. rust...

Adding an extra use case for this that I've seen a couple times and recently in [this slack thread](https://knative.slack.com/archives/C0186KU7STW/p1633363359185300): there are cases - especially bursty eventing workloads - where at...

/reopen The bit that doesn't work is the postStart idea, which was a little side comment, not the main point of the issue (the thread's a bit confusing I guess...

I think we need to settle on what the right behaviour is here: hanging seems pretty wrong and unexpectedly different from k8s, but should we scale up (so, ignore non-ready...

/remove-lifecycle stale. /reopen /lifecycle frozen

so how do we want to proceed on this? Would a feature proposal doc to hash out the details and any foreseeable edge cases be the best next step?

cool - @skonto happy to work together on that if you like?