I'm confused about how Fleet handles directories containing Helm templates. I have e.g.

bioapp/influxdb/routes/httproute.yaml

containing a helm template like this:

{{- if .Values.httpRoute.enabled -}}
apiVersion: <http://gateway.networking.k8s.io/v1|gateway.networking.k8s.io/v1>
kind: HTTPRoute
metadata:
  name: influxdb-httproute
spec:
  parentRefs:
    {{- with .Values.httpRoute.parentRefs }}
      {{- toYaml . | nindent 4 }}
    {{- end }}
  {{- with .Values.httpRoute.hostnames }}
  hostnames:
    {{- toYaml . | nindent 4 }}
  {{- end }}
  rules:
    {{- range .Values.httpRoute.rules }}
    {{- with .matches }}
    - matches:
      {{- toYaml . | nindent 8 }}
    {{- end }}
    {{- with .filters }}
      filters:
      {{- toYaml . | nindent 8 }}
    {{- end }}
      backendRefs:
        {{- with .backendRefs }}
          {{- toYaml . | nindent 8 }}
        {{- end }}
    {{- end }}
{{- end }}

With

values.yaml

in the same directory providing the appropriate values to fill. This fails with

"error while running post render on files: invalid character '{' looking for beginning of object key string"

, which I assume means it is trying to create the resource as raw yaml. But if I create

Chart.yaml

in the directory to force it to be interpreted as helm, I get a rendered Bundle resource with

Spec.Resources.Content

containing the raw file, but nothing actually gets created. Is it allowed to use Helm templates with Fleet? Where can I find logs and/or documentation on what Fleet is doing here?