Altinity / Altinity/helm-charts
securityContext bug
@joshleecreates is already working on this.
Since Dec 3, 2025.
- Dominant language
- Python
- Stars
- 57
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
Uncomment the podSecurityContext and securityContext sections of the values.yaml and deploy.
Current behavior:
The values for runAsUser and runAsGroup are incorrectly placed in the resulting pods. They show up in the security context of the pod, instead of the container. fsGroup does not carry through at all.
Example:
spec:
containers:
securityContext: {}
securityContext:
runAsGroup: 101
runAsUser: 101
Expected behavior:
The pod scope securityContext should contain the fsGroup value. The container level scope should contain runAsUser and runAsGroup.
spec:
containers:
securityContext:
runAsGroup: 101
runAsUser: 101
securityContext:
fsGroup: 101
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.