Multiple k8s resources that use Tilt-controlled images breaks logging about tilt HOT 4 CLOSED

thanks for the report! This is something we're actively working on fixing.

Question: what do you think should happen? I go back and forth between whether Tilt should show the Job and Deployment as separate lines in the UX, vs grouping them together in a combined view with combined logs.

One workaround we've seen is to use a different image name for the two jobs, and make one name an alias of the other.

from tilt.

@nicks thanks for letting me know. With help from @dbentley, I ended up created explicit k8s_resource by filtering my helm chart. That is working nicely now.

I think I would like to see them separately -- I generally use namespace:kind:name as the unique key when dealing with k8s resources.

from tilt.

Ya, k8s_resource is a good workaround too. And ya, segmenting by namespace:kind:name makes sense. We're currently talking about changing how we do segmenting, though we might write up a spec on it first.

from tilt.

@samhagan this should be fixed in new versions of Tilt. We no longer break images out by image by default: we also take in to account the CMD/entrypoint.

Let me know if this makes things better for you!

from tilt.