Set securityContext on namespace-metadata job container

[akorp]

What problem are you trying to solve?

Additional security. It is a best practice in security to run container with a minimum required securityContext. Many kubernetes users, including us, have constraints in cluster prohibiting high privileges.

How should the problem be solved?

Add securityContext for the namespace-metadata job.

  privileged: false
  allowPrivilegeEscalation: false
  runAsNonRoot: true
  readOnlyRootFilesystem: true

As described at #6638, image might change in the future, but any image unlikely to require high privileges for its taks described in PR.

Any alternatives you've considered?

Could not find other alternatives for the described solution.

How would users interact with this feature?

No response

Would you like to work on this feature?

No response

[alpeb]

Note that this is being addressed indirectly by #9719

[alpeb]

Addressed in #9719