Joe Julian

I think this should be properly handled by helm's [resource ordering](https://github.com/helm/helm/blob/12f1bc0acdeb675a8c50a78462ed3917fb7b2e37/pkg/releaseutil/kind_sorter.go).

GitHub doesn't allow folks to be assigned that don't meet some criteria (no idea what criteria), but please feel free to open a PR referencing this issue.

I don't have an answer to whether they should or not, but release dates are governed by https://github.com/helm/community/blob/main/hips/hip-0002.md

Can I suggest a different approach to Unmarshalling multi-document yaml? What about using this example? https://go.dev/play/p/MZNwxdUzxPo

I've tried the method you're suggesting, in the past, and something caused it to break mid-file. I can't remember what it was though.

@jkroepke I've been wondering that, too. Maybe the helm mailing list or, if you can attend, the [helm developer call](https://docs.google.com/document/d/1d-6xJEx0C78csIYSPKJzRPeWaHG_8W1Hjl72OJggwdc/edit)?

Just to be clear, triage folks are not code maintainers. We triage issues. Our feedback on PRs has exactly as much weight as anybody else in the community.

Closing as duplicate

This seems to be because the build process switched to building static binaries. Static builds use Go's built-in DNS resolver that does not account for any OS specific configurations.

IMHO, shipping static binaries is the correct thing for the helm project to do. Dynamically linking should be left to downstream packagers otherwise the release binaries will only work on...