feat: Add custom settings for pod- and containerSecurityContext instead of global securityContext
this one was merged in a custom branch and never got it into master so new try (https://github.com/imgproxy/imgproxy-helm/pull/157)
definitely needed 👍
@DarthSim @dragonsmith can somebody pls take a look here?
Hey @kaufmo! Please don't rename values. This will break things for everyone who uses them.
As Darthsim mentioned above, though, this approach would break backward compatibility. There’s also #201, which addresses the issue in the same way but without renaming. I appreciate your contribution! At this point, I think the other PR should take precedence. Thank you again for your efforts here.
However, naming here is much more logical
Thank you again for implementing this. I've merged #198, and fixed the naming as you proposed here, with deprecation warning for an old value. Closing this for now.