Bartlomiej Plotka

Generally make sense, thanks for the quick response. This to me sounds like a nice separation of concerns 👍🏽 +1 on render-only being a separate command. I understand the vision...

I totally understand the use case here, but I think this should be the role of CRD to allow those. I am experimenting with some flexible customize approach on https://github.com/observatorium/rndr

Correct - just different provider. The interesting (tricky) thing is to map YAML API to template parameters. It might be just a separate configuration file.

Also see next idea: https://github.com/brancz/locutus/issues/50 - to see if we agree on common direction of Locutus - I think there is overlap (:

Zen repo ((:

I am build some skeleton of the docs for https://github.com/cncf/sig-observability/issues/19 and will definitely will link this zen there. I think it would be nice if maintainers / community of each...

What huge means? (: Performance optimiations is never ending story. We need to find out if: * Perf improvements are worth it, prioritize it. Is tool unusable? How much memory...

Yea, The way format is to obtain profiles and figure out the problematic spot (: Feel free to read more about it here: https://jvns.ca/blog/2017/09/24/profiling-go-with-pprof/ `pprof` endpoint should be already available....

Perfect thanks for this. It's currently hard or impossible to move Memory Arrow frame between processes natively. That's why Flight is helpful here. > Apache Arrow Flight is a completely...

Nice 👍🏽