Resources considered in --wait option during helm install

[apurvakg]

Hey team,
I would like to know that what are the resources considered in the --wait option during install. I can see that all the resources are not considered during --wait command in helm install. I would like to know the list of resources that are considered as of now. My use case is to wait for pods created by daemonset to be up. Is daemonset considered in wait command? If not is there a way we can include it, or wait for it to be up?

and another question if I use --atomic command(for automatic rolback) can i use --timeout option with that too, to specify a timeout for the wait condition it automatically sets

[gjenkins8]

Unfortunately, the logic for what is waited for, and how. Is not well documented. The code has the details: https://github.com/helm/helm/blob/main/pkg/kube/ready.go#L92-L205 . Daemonsets are waited for.

---

I suspect if you use the --timeout option. The same value is used for both the upgrade and rollback-on-failure (the atomic flag). Would need to dig into docs (or code) to confirm.