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
❯ kustomize version
5.3.0
❯ kustomize build . --enable-helm
Error: map[string]interface {}(nil): yaml: unmarshal errors:
line 37: mapping key "affinity" already defined at line 23
Expected behavior
A clear and concise description of what you expected to happen.
YAML files should be rendered without any errors.
Additional context
Add any other context about the problem here.
Defining .values.affinity leads to duplicate spec.affinity definitions, I guess:
Describe the bug
It seems that it's impossible to specify affinity for pod assignment.
Environment
Provide accurate information about the environment to help us reproduce the issue.
To Reproduce
Steps to reproduce the behavior:
Then try to generate YAML files:
Expected behavior
A clear and concise description of what you expected to happen.
YAML files should be rendered without any errors.
Additional context
Add any other context about the problem here.
Defining .values.affinity leads to duplicate
spec.affinity
definitions, I guess:trident/helm/trident-operator/templates/deployment.yaml
Lines 30 to 57 in 6f311fc
The text was updated successfully, but these errors were encountered: