<p>I would like to see the output from my pre-install/post-install helm hooks when using <code>skaffold dev</code>, but this does not seem to work.</p>
<p>Which filters does skaffold use to get all the pods for log tailing? Is there a way to force skaffold to pick up the hooks by applying some labels (e.g. <code>skaffold.dev/run-id: static</code>) ?</p>
<p><strong>Context</strong></p>
<p>Doing dev with local docker, the image building is pretty fast, so for some use cases there is no need to use file sync and special dev-mode container images with file watching inside.</p>
<p>There is this feature request: <a href="https://github.com/GoogleContainerTools/skaffold/issues/1441" rel="nofollow noreferrer">https://github.com/GoogleContainerTools/skaffold/issues/1441</a>, but this is for adding hooks to skaffold itself.</p>
<p>The pods created by helm hooks are not removed (<a href="https://github.com/GoogleContainerTools/skaffold/issues/2876" rel="nofollow noreferrer">https://github.com/GoogleContainerTools/skaffold/issues/2876</a>), but this is expected behavior for <code>helm delete</code>.</p>

<p>Thanks @acristu for the question. Skaffold dev here.
Currently, skaffold is unaware of pods deployed in the pre and post helm hooks.
The reason, we don't parse the manifests in these hooks and hence can't transform those to add the required label <code>skaffold.dev/run-id</code></p>
<p>Currently there is no way to force skaffold to pick up the logs from these pods/containers</p>
<p>That said we had a pending feature request to extend the current log configuration to include <code>resourceType</code> or <code>resourceName</code> like <code>portForward</code> section</p>
<pre><code>portForward:    #   describes user defined resources to port-forward.
- resourceType: #   Kubernetes type that should be port forwarded.           
  resourceName:
</code></pre>
<p>Supporting this in skaffold would be great idea.</p>
