[Bug]: neo4j-cronjob should allow securityContext setup at the container and pod level

[aguealejandro]

Contact Details

[email protected]

What happened?

We are running database backup jobs using the neo4j-cronjob helm chart, however we are unable to get it fully to work in AKS. The main reason is that securityContext.allowPrivilegeEscalation needs to be set to false at the CONTAINER level. Currently securityContext is only set at the POD Level

helm-charts/neo4j-admin/templates/neo4j-cronjob.yaml

Line 41 in 8bffca1

securityContext: {{ .Values.securityContext | toYaml | nindent 12 }}

, as we can see on the following documentation, it needs to be done at the container level as well https://kubernetes.io/docs/tasks/configure-pod-container/security-context/

##Alternatives
Currently we had to fork the repo and clone the neo4j-admin chart into our repo in order to unblock ourselves, but ideally we would like to point to the official updated version.

Chart Name

Neo4j Admin

Chart Version

5.12.0

Environment

Microsoft Azure

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct