You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lots of proxy and watcher stuff in the milestone and it's in a good state atm (no big follow-ups planned on my end in stable), but have plans for unstable stuff in stream sharing. shouldn't let that block a release though.
jotting down some provisional highlights (will edit in links/callouts later as appropriate).
Runtime: Decreased Memory Usage from watcher
Buffering of initial pages / init streams is no longer a mandatory process with watcher::Event gaining new Init, InitApply, and InitDone events. These events are read on the store side maintaining the atomicity/readiness guarantees for reflector and Store users.
This should provide a significant memory decrease for watcher users (both with and without stores). See #1494 for benchmarks.
The downside is a breaking change to watcher::Event. Plain usage of watcher / reflector / Controller should generally not need to change anything, but custom stores / matches on watcher::Event will need an update. If you are writing custom stores, the new signals should be helpful for improved caching.
lots of proxy and watcher stuff in the milestone and it's in a good state atm (no big follow-ups planned on my end in stable), but have plans for unstable stuff in stream sharing. shouldn't let that block a release though.
jotting down some provisional highlights (will edit in links/callouts later as appropriate).
Runtime: Decreased Memory Usage from
watcher
Buffering of initial pages / init streams is no longer a mandatory process with
watcher::Event
gaining newInit
,InitApply
, andInitDone
events. These events are read on the store side maintaining the atomicity/readiness guarantees forreflector
andStore
users.This should provide a significant memory decrease for
watcher
users (both with and without stores). See #1494 for benchmarks.The downside is a breaking change to
watcher::Event
. Plain usage ofwatcher
/reflector
/Controller
should generally not need to change anything, but custom stores / matches onwatcher::Event
will need an update. If you are writing custom stores, the new signals should be helpful for improved caching.Thanks to
@fabriziosestito
via Kubewarden for #1494 . Follow-ups for this feature: #1499 and #1504.Client: HTTP Proxy Support
Support is now introduced under the
http-proxy
feature pulling in hyper-http-proxy complementing the already existingsocks5
proxy feature.Thanks to
@aviramha
via MetalBear for the support in #1496, with follow-ups #1501 + #1502The text was updated successfully, but these errors were encountered: