Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cant install chart v0.5.0 #178

Closed
isality opened this issue Aug 15, 2022 · 6 comments · Fixed by #182
Closed

cant install chart v0.5.0 #178

isality opened this issue Aug 15, 2022 · 6 comments · Fixed by #182

Comments

@isality
Copy link

isality commented Aug 15, 2022

h1 there

i cant install v0.5.0. I got error:

Error: template: cert-manager-istio-csr/templates/serviceaccount.yaml:3:7: executing "cert-manager-istio-csr/templates/serviceaccount.yaml" at <ne .Values.image.pullSecretName "">: error calling ne: incompatible types for comparison

Use --debug flag to render out invalid YAML

I added pullSecretName: "" in values.yaml, object image and helm template works fine. Could your check this?

@JoshVanL
Copy link
Contributor

Hi @isality, this looks to be a duplicate of #175
Can you update your helm version, and try again?

@isality
Copy link
Author

isality commented Aug 17, 2022

H1!

I updated helm to version.BuildInfo{Version:"v3.9.3", GitCommit:"414ff28d4029ae8c8b05d62aa06c7fe3dee2bc58", GitTreeState:"clean", GoVersion:"go1.17.13"}

And right now i can do helm template istio-csr ./

---
# Source: cert-manager-istio-csr/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
imagePullSecrets:
  - name: 
metadata:
  labels:
    app.kubernetes.io/name: cert-manager-istio-csr
    helm.sh/chart: cert-manager-istio-csr-v0.5.0
    app.kubernetes.io/instance: istio-csr
    app.kubernetes.io/version: "v0.5.0"
    app.kubernetes.io/managed-by: Helm
  name: cert-manager-istio-csr

But i think it's not okay, when a non-existent field is accessed. See https://github.com/cert-manager/istio-csr/blob/v0.5.0/deploy/charts/istio-csr/templates/serviceaccount.yaml#L3

Thx

@JoshVanL
Copy link
Contributor

Could you explain this a bit more, I’m not sure I follow?

But i think it's not okay, when a non-existent field is accessed

@isality
Copy link
Author

isality commented Aug 17, 2022

Ok, see

Your trying to get value .Values.image.pullSecretName here, but in values.yaml your haven't a field pullSecretName in object image.

@nitishkrishna
Copy link
Contributor

+1 seeing the same issue, its referring to a non-existing value

@craigmunro
Copy link
Contributor

Same problem here. I've raised #182 to fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants