-
Notifications
You must be signed in to change notification settings - Fork 112
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
Error calling ne: incompatible types for comparison #1241
Comments
Also is there a way to disable all validation? Thanks for answering! |
Please try updating your Helm cli. At minimum, we use helm version 3.14. |
@Archer-Li just checking in if you were able to update helm CLI, and if that helped |
Hello, We are using Terraform to installing K8s-helm charts. Here's the list of versions we were using:
We have attempted to update helm version with latest: 3.0.0-pre1, but not getting any luck yet |
Let me check with my own terraform deployed instance. Can you share the |
Sure, here's the definition:
We do have the helm with same definition deployed successfully on our linux/arm64 cluster. But linux/amd64 is keeps giving us type check issues. |
template: k8s-monitoring/templates/validations.yaml:5:4: executing "k8s-monitoring/templates/validations.yaml" at <include "destinations.validate" .>: error calling include: template: k8s-monitoring/templates/destinations/_destination_validations.tpl:40:46: executing "destinations.validate" at <ne $destination.protocol "http">: error calling ne: incompatible types for comparison
I think
(ne $destination.protocol "http")
will be evaluated for every destination item (including loki, prometheus...etc.). Without protocol set will immediately causing mismatch type error.Helm version: 2.0.10
Helm value.yaml:
The text was updated successfully, but these errors were encountered: