Nick Santos

have you seen https://github.com/tilt-dev/tilt-extensions/tree/master/list_dependencies ?

ya, podmetrics are entirely handled by kubernetes controllers. the whole point of podmetrics is that the services running on kubernetes know nothing about them. as for why it's not working...

(as a side note, i was able to reproduce the same behavior with both the Cloud Integration cli and the vanilla `com.docker.cli` one)

Compose supports `COMPOSE_PARALLEL_LIMIT`. Maybe it would be good if `buildx bake` respected this as well? https://docs.docker.com/compose/environment-variables/envvars/#compose_parallel_limit Alternatively, maybe add a `BUILDX_PARALLEL_LIMIT` to match the compose CLI?

cool! thanks.

for what it's worth, it seems like this only happen when a Device is specified on EventStream. if you use per-host streams (rather than per-disk streams), everything works ok.

Hi @cindymullins-dw ! Ah, I think I just realized what causes it. Try these repro steps: ``` telepresence quit -s telepresence helm upgrade telepresence version ``` My theory of what's...

Ok, narrowed down the bug: telepresence uses envoy to manage agent traffic. envoy, by default, rejects all http 1.0 requests. https://github.com/envoyproxy/envoy/issues/170 nginx, by default, sends http 1.0 requests. http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_http_version it...

The only trickiness is we'll have to do a version check on docker compose, since this requires 2.17+

@lizzthabet curious how this dovetails with other "organizing containers" work you've been doing.