Update Helm Chart for Dynamic Security Contexts

This MR adds the ability to dynamically configure securityContext and containerSecurityContext through the values.yaml file in your Helm chart. This change addresses the need for more granular security settings due to the deprecation of Kubernetes pod security policies (PSP).

What's Changed:

• You can now tweak security settings for pods and containers directly in values.yaml, making it flexible to meet different security needs.
• This update helps you stay in line with the latest Kubernetes security practices by utilizing native security context capabilities.

added 1 commit

• 4f608750 - Nest security context into allocator value to improve readability

Compare with previous version

@toby-acnodal The pipeline appears to fail as a result of no arm runners. Let me know if you need anything specific from me to satisfy that test.

assigned to @caboteria

changed milestone to %Desmodromic

added Enhancement label

Sorry that I missed this for so long! I rebased your fixes to the latest main branch and had to tweak the template value a little: in the deployment securityContext I had to use an indent of 8 instead of 6:

https://gitlab.com/purelb/purelb/-/blob/20240422-update-security-context/build/helm/purelb/templates/deployment.yaml?ref_type=heads#L58

The code's in this repo in the 20240422-update-security-context branch. If it looks good to you I'll merge it to main.

Oh, by the way, if we drop the ball like this again please feel free to join our slack channel at https://kubernetes.slack.com/archives/C01BCB7U031 and rattle our cage.

No problem at all! Appreciate you getting around to it!

Merged manually with commit 32ad2586

Thank you for the improvement!

closed