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

[BUG] the chart creates a duplicate security context under certain conditions #428

Open
wy100101 opened this issue Jul 2, 2024 · 2 comments · May be fixed by #458
Open

[BUG] the chart creates a duplicate security context under certain conditions #428

wy100101 opened this issue Jul 2, 2024 · 2 comments · May be fixed by #458
Labels

Comments

@wy100101
Copy link

wy100101 commented Jul 2, 2024

Describe the bug
the forecastle chart creates a duplicate security context when you set .Values.forecastle.deployment.securityContext resulting in an invalid manifest.

To Reproduce
helm deploy forecastle with securityContext set under .Values.forecastle.deployment.securityContext will result in the following error:
Helm install failed for release forecastle/forecastle with chart [email protected]: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors:
line 46: mapping key "securityContext" already defined at line 35

Expected behavior
A clean helm install

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • Operator Version:
  • Kubernetes/OpenShift Version: EKS

Additional context
Add any other context about the problem here.

@bnallapeta
Copy link

@wy100101 Ack. Will work on it.

@karl-johan-grahn
Copy link
Contributor

The issue can be reproduced with helm template.

Unit test could be added with d3adb5/helm-unittest-action. Example tests: https://github.com/d3adb5/helm-unittest-action/blob/master/example-chart/tests/example_test.yaml

@karl-johan-grahn karl-johan-grahn changed the title [BUG] [BUG] the chart creates a duplicate security context under certain conditions Aug 28, 2024
@aslafy-z aslafy-z linked a pull request Nov 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants