Revert "fix(operator): Make snitch UBI image non-root"#2654
Merged
Conversation
This reverts commit 0a1b056. Signed-off-by: Aryan Bakliwal <[email protected]>
AryanBakliwal
force-pushed
the
revert-snitch-nonroot
branch
from
1a23463 to
9f6fbf7
Compare
AryanBakliwal
requested review from
Aryan-sharma11,
achrefbensaad and
charankamal20
achrefbensaad
approved these changes
Jun 8, 2026
charankamal20
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This reverts commit 0a1b056.
Purpose of PR?:
Snitch is deployed to run as root by the operator since it requires root privileges. The change to run snitch as non-root in its container was added to pass RedHat preflight check but running snitch as root was intended, and previous certified images on RedHat also did not run as non-root user and were certified using manual review.
Fixes #
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered:
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>