Velvet Star Monitor

Standout celebrity highlights with iconic style.

updates

chart metadata (Chart.yaml) missing on helm upgrade

Writer Matthew Martinez

I was following this blog post and at this command,

helm upgrade --install airflow airflow/ \ --namespace airflow \ --values values.yaml

I got this error. in airflow: chart metadata (Chart.yaml) missing but I actually have the Chart.yaml file under airflow/.

$ ls
Chart.yaml charts requirements.yaml tiller.yaml
Icon? requirements.lock templates values.yaml

helm version & kubectl pod below

$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
$ kubectl get pods --namespace kube-system
NAME READY STATUS RESTARTS AGE
coredns-fb8b8dccf-9z8v5 1/1 Running 3 6h
coredns-fb8b8dccf-wdtpl 1/1 Running 3 6h
etcd-minikube 1/1 Running 1 6h
kube-addon-manager-minikube 1/1 Running 1 6h
kube-apiserver-minikube 1/1 Running 1 6h
kube-controller-manager-minikube 1/1 Running 1 6h
kube-proxy-m4whq 1/1 Running 0 2h
kube-scheduler-minikube 1/1 Running 1 6h
kubernetes-dashboard-79dd6bfc48-5z9cx 1/1 Running 3 6h
storage-provisioner 1/1 Running 3 6h
tiller-deploy-8458f6c667-wmv62 1/1 Running 1 4h

Could someone help to fix it?

4 Answers

I also had the error with Airflow. I noticed that you have to respect the folder structure. This example will fail:

./charts ./charts/airflow ./charts/template ---> will produce the error 

While this folder structure will work:

./charts ./charts/airflow templates --> will work

The directory must not contain a directory with the same name as the chart name.

For anyone stumbling on this, the answer is over here:

1

detailed information about helm upgrade and requirements you can find here:

In your example please go to airflow-kube-helm directory and run:

helm upgrade --install airflow ./airflow/ --namespace airflow --values ./airflow/values.yaml

In case the previously deployment failed, please use helm delete (your_release_name) --purgeMore info about this issue here and here

Hope this help. Please share with your findings.

11

I had a similar issue when trying to install Ingress Nginx using Helm.

For me I put the helm commands in a script called install.sh, however, I was not running the file within the folder where the install.sh script.

I was running it this way sh ingress-nginx/install.sh, and it was returning the error.

All I had to do was cd into the folder and run the script:

cd sh ingress-nginx
sh install.sh

And it ran successfully this time.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.