Issue 440: Added support to run zookeeper operator as non-root

[anishakj]

Signed-off-by: anishakj [email protected]

Change log description

Made changes in operator charts to configure security context.
Updated hook image to 1.23.2
Added options in hooks to configure security context.
Active Delay seconds is removed in pre-delete-hooks

Purpose of the change

Fixes #440

What the code does

Provide support to run zookeeper-operator as non-root user

How to verify it

Verify able to run zookeeper-operator as non root user

[codecov]

Codecov Report

Merging #441 (d2ebb5a) into master (b150f81) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #441   +/-   ##
=======================================
  Coverage   84.11%   84.11%           
=======================================
  Files          12       12           
  Lines        1643     1643           
=======================================
  Hits         1382     1382           
  Misses        177      177           
  Partials       84       84           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b150f81...d2ebb5a. Read the comment docs.

[jkhalack]

LGTM

[HoustonPutman]

Maybe I'm missing something here, but it doesn't look like the {{Values.securityContext}} is used anywhere in the zookeeper-operator deployment. The functionality was only added for the hooks...

[janhoy]

I'm running into the same, trying to specify securityContext for the zookeeper-operator pod, which does not work. Is there a know workaround to this, and is there plans to add it in next release?

[lfloris]

Has there been any progress on the issue above at all? Running into the same issue where zookeeper operator pod does not run on restricted Kubernetes environments.