John Howard
John Howard
We worked around this via ```rust static LOG_HANDLE: OnceCell = ... pub fn enabled(target: &'static str, level: &tracing::Level) -> bool { if let Some(handle) = LOG_HANDLE.get() { handle .with_current(|f| f.filter().would_enable(target,...
```diff diff --git a/pilot/pkg/xds/eds.go b/pilot/pkg/xds/eds.go index 93f13e4627..f62e2942eb 100644 --- a/pilot/pkg/xds/eds.go +++ b/pilot/pkg/xds/eds.go @@ -206,6 +206,9 @@ func (eds *EdsGenerator) buildEndpoints(proxy *model.Proxy, // generate eds from beginning { l := builder.BuildClusterLoadAssignment(eds.EndpointIndex)...
haven't seen similar and this codepath has changed a lot; closing for now
Another example use case is to have a label like `test/enable-verbose-logs` to turn on super verbose logs on tests that are normally disabled due to costs. This might be a...
I wrote up more about shell tracing. Not directly related but likely to be used in parallel: https://blog.howardjohn.info/posts/shell-tracing/
I think (1) is valid, but (2) is not, IMO. This actually doesn't even work in Kubernetes core with just basic Service routing. The Endpoint being generated is the _signal...
(1) should be enforced without any status - changes to a route should be zero downtime or routes are effectively immutable, IMO.
> For (2), does it seem reasonable to block the data-plane routing updates until the Service backends are resolved in the gateway api control plane? This would be more complex,...
> We want to avoid mounting of any kind for declarative execution. Most use cases we've seen can be formulated as running a priviledged function once instead of repeatedly as...