You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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
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 fileVersion 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 fixedWhat you expected to happen:
The helm install should succeed without warnings
How to reproduce it (as minimally and precisely as possible):
Create repro.yaml:
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 affinitycouchdb-helm/couchdb/values.yaml
Line 87 in deb055f
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.
The text was updated successfully, but these errors were encountered: