Chart.yaml generated doesn't match template

[benmathews]

It appears that the generated Chart.yaml is coming from helm, not from your template. If I create a foo chart, then the contents of Chart.yaml are

apiVersion: v1
description: A Helm chart for Kubernetes
name: foo
version: 0.1.0

The remainder of your templates though are included.

$ ls foo/
charts/            .helmignore        PERSISTENCE.md     requirements.yaml  values.yaml        
Chart.yaml         Jenkinsfile        README.md          templates/         
$ ls foo/templates/
certificate.yaml  daemonset.yaml   _helpers.tpl  NOTES.txt  role-binding.yaml  secret.yaml           service.yaml
configmap.yaml    deployment.yaml  job.yaml      pvc.yaml   role.yaml          service-account.yaml

[andrewhowdencom]

Indeed. I haven't found a way to get around this limitation -- I usually just copy and paste it in. Perhaps we can open a bug in the upstream helm project?

Edit: Referenced here https://github.com/kubernetes/helm/blob/master/docs/charts.md#chart-starter-packs

[benmathews]

Sounds like a good idea. There is no documentation that I could find on the starter scaffolding feature. Yours and one other project are all I could find as a sample to base my own efforts off of.

…

On Tue, Dec 5, 2017 at 7:24 AM, Andrew Howden ***@***.***> wrote: Indeed. I haven't found a way to get around this limitation -- I usually just copy and paste it in. Perhaps we can open a bug in the upstream helm project? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAbPrHiMUS7-Kjp6yhuExVUkt5saB-2gks5s9VICgaJpZM4Q1XtM> .

-- Ben Mathews