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

Warning during install: Skipped value for affinity: Not a table #32

Closed
borigas opened this issue Jun 19, 2020 · 0 comments · Fixed by #34
Closed

Warning during install: Skipped value for affinity: Not a table #32

borigas opened this issue Jun 19, 2020 · 0 comments · Fixed by #34

Comments

@borigas
Copy link
Contributor

borigas commented Jun 19, 2020

Describe the bug
I get a warning coalesce.go:160: warning: skipped value for affinity: Not a table. when trying to install with affinity set in my values file

Version of Helm and Kubernetes:
Helm: 3.2.1
Kubernetes: 1.17.5

What happened:
When installing, I get a warning: coalesce.go:160: warning: skipped value for affinity: Not a table. Warnings cause my deployment pipeline to abort, so I need to get this fixed

What you expected to happen:
The helm install should succeed without warnings

How to reproduce it (as minimally and precisely as possible):

Create repro.yaml:

couchdbConfig:
  couchdb:
    uuid: 123

affinity:
  podAntiAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchExpressions:
            - key: "app"
              operator: In
              values:
              - couchdb
        topologyKey: "kubernetes.io/hostname"

Then run helm install my-name couchdb/couchdb -f repro.yaml

Anything else we need to know:
It seems to be tied to having affinity: defined in values.yaml without any children. If I comment out this line, the release succeeds without errors and creates the affinity

I know this isn't the only place that a key is defined without children though, so I'm trying to figure out if there's a better way.

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.

1 participant