I have a silly problem that probably has an easy answer, but fleet has so many rich parameters it can be hard to handle specific cases. My fleet.yaml is in a git directory along side a 3rd-party Helm chart (but it could be a custom one of ours). I'm referencing it this way: helm: repo: "" chart: "./vault-operator-1.22.0.tgz" version: "" and I get the following error from Fleet: level=fatal msg="no chart name found" The name of the chart is inside the Helm chart tarball so what's the problem? I've seen folks refer to remote such charts using: chart: "https://github.com/rancher/fleet-examples/releases/download/example/guestbook-0.0.0.tgz" Which looks like mine just using http instead of local.