feat(core): Change Operator and Builder Pod user as non root 1000 #4407
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Since the new builder pod is configured to run with non root user and a persistent volume has been created there have been some permission/copy issues I fixed while working on #4297. The permissions issues can be fixed two different way on kubernetes security : extend root user or extend non-root user.
Since it make more sense to try to avoid root (as a general rule) and some Dockerfile already use user with ID 1000 (same for group ID), I made some first modifications to try to have more non-root user for operator and builder pods.
There are also some warnings on integration containers security validations, but they will be dealt with #4297.
Description
Release Note