Nick Santos

Yes, tilt's docker_build currently works by creating a connection to the builder at startup, before tiltfile execution. there's currently not a way to configure that connection from the tiltfile.

It's not impossible to add, just non-trivial. The workaround right now is to set DOCKER_BUILDKIT=0 before tilt starts. I guess you could also use a `custom_build` that sets it, though...

I believe this is working as expected. `kubectl port-forward service/my-service ...` picks one pod to forward traffic to. it doesn't attempt to do any load balancing across multiple endpoints. You...

i talked to the Compose people about how they handle this problem. The code is here: https://github.com/docker/compose/blob/v2/cmd/formatter/logs.go where they don't do any truncation at all; they just expand the prefix...

thanks for the report! So I understand the problem. But I'm not sure how we should fix it or what the correct behavior should be. When you mount a local...

yep, that's what i'd expect, because you're mounting those files into the container itself under `volumes`

one idea i played around with was to do something like: ``` k8s_custom_deploy( ..., port_forwards=[ port_forward(8080, 8080, selector={"app": "labelA"}), port_forward(8081, 8081, selector={"app": "labelB"}) ] ) ``` or you could go...

i also am not sure if there's a way to do this without having to encode a lot of the chart internals in the tiltfile, which feels odd

One way to workaround this is to use k8s_attach. So you might have a chart that creates multiple deployments, and you can use `k8s_attach` to create separate port-forwards: ``` load('ext://k8s_attach',...

This is currently working as intended. `k8s_grace_period` is a pretty blunt hammer - it tells tilt to wait longer, but doesn't have any deep knowledge of kubernetes Job backoff limit...