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

Invalid Helm template in v0.30.1 #1453

Open
drmaciej opened this issue Jul 2, 2024 · 7 comments
Open

Invalid Helm template in v0.30.1 #1453

drmaciej opened this issue Jul 2, 2024 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@drmaciej
Copy link

drmaciej commented Jul 2, 2024

What version of descheduler are you using?

descheduler version: v0.30.1

Does this issue reproduce with the latest release?
Yes

Which descheduler CLI options are you using?

cmdOptions:
  v: 4

Please provide a copy of your descheduler policy config file

resources:
  requests:
    cpu: 250m
    memory: 256Mi
  limits:
    cpu: 250m
    memory: 256Mi

commonLabels:
  app: descheduler

podLabels:
  app: descheduler

schedule: "30 * * * *"

cmdOptions:
  v: 4

deschedulerPolicy:
  evictLocalStoragePods: true
  ignorePvcPods: true
  strategies:
    LowNodeUtilization:
      enabled: true
      params:
        nodeResourceUtilizationThresholds:
          thresholds:
            cpu: 80
            memory: null
            pods: null
          targetThresholds:
            cpu: 85
            memory: null
            pods: null
        namespaces:
          exclude:
            - kube-system
    RemoveDuplicates:
      enabled: false
    RemovePodsHavingTooManyRestarts:
      enabled: false
    RemovePodsViolatingNodeTaints:
      enabled: false
    RemovePodsViolatingNodeAffinity:
      enabled: false
    RemovePodsViolatingInterPodAntiAffinity:
      enabled: false
    RemovePodsViolatingTopologySpreadConstraint:
      enabled: false

tolerations:
  # redacted
  - key: "***"
    operator: "Equal"
    value: "true"
    effect: "NoSchedule"

What k8s version are you using (kubectl version)?

kubectl version Output
$ kubectl version
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.1-eks-1de2ab1

What did you do?
Upgrade from 0.29.0 to 0.30.1

What did you expect to see?
A working Helm deployment

What did you see instead?

│ Error: template: descheduler/templates/cronjob.yaml:84:23: executing "descheduler/templates/cronjob.yaml" at <ne $value nil>: error calling ne: incompatible types for comparison
│
│   with helm_release.descheduler,
│   on helm.tf line 196, in resource "helm_release" "descheduler":
│  196: resource "helm_release" "descheduler" {

appears to have been introduced in a09c4d2.

I had to downgrade to 0.29.0 because 0.30.0 didn't work due to #1420.

@drmaciej drmaciej added the kind/bug Categorizes issue or PR as related to a bug. label Jul 2, 2024
@a7i
Copy link
Contributor

a7i commented Jul 2, 2024

Would you please try this and see if you get the same error?

cmdOptions:
  v: "4"

@drmaciej
Copy link
Author

drmaciej commented Jul 2, 2024

Yes, it results in the same error

@a7i
Copy link
Contributor

a7i commented Jul 6, 2024

I tried this using the helm CLI and no issues:

$ cat /tmp/values.yaml
cmdOptions:
  v: 4


$ helm template deschduler ./descheduler -f /tmp/values.yaml | grep bin/descheduler -A 3
                - /bin/descheduler
              args:
                - --policy-config-file=/policy-dir/policy.yaml
                - --v=4

What is your helm version? My Helm Version:

helm version
version.BuildInfo{Version:"v3.14.3", GitCommit:"f03cc04caaa8f6d7c3e67cf918929150cf6f3f12", GitTreeState:"clean", GoVersion:"go1.22.1"}

@jordi-crespo
Copy link

Same error for me.

My helm version is:

version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}

@shahar-h
Copy link
Contributor

It works for helm >= 3.8.0.

@a7i
Copy link
Contributor

a7i commented Jul 30, 2024

Given that Helm v3.7.0 is almost 3 years old, we can close this issue? Thoughts @drmaciej and @jordi-crespo ?

@drmaciej
Copy link
Author

I'm on Helm 3.15.3, but it turns out it wasn't the issue. The issue was in an old Terraform provider for Helm - I upgraded that to latest and the issue is now resolved.

Thanks for helping!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants