Bug 2167304: security: run the crash collector as ceph user

[subhamkrai]

The crash collector does not have the command line arguments to run as ceph user id 167, so we set the security context to run as the ceph user in the main crash collector container.

Signed-off-by: Travis Nielsen tnielsen@redhat.com
(cherry picked from commit df6d7af)

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide).
• Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

[subhamkrai]

cc @travisn @agarwal-mudit

[subhamkrai]

Linters/pylint ci error is fixed in upstream versions

[travisn]

Linters/pylint ci error is fixed in upstream versions

Please also cherry-pick the fix into this PR for rook#11606 so we can get a clean linter.

[subhamkrai]

Linters/pylint ci error is fixed in upstream versions

Please also cherry-pick the fix into this PR for rook#11606 so we can get a clean linter.

done

[subhamkrai]

@travisn ready to go in?

[travisn]

What BZ is this for? We need Bug *: in the PR title

[openshift-ci]

@subhamkrai: This pull request references Bugzilla bug 2167304, which is valid.

2 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @nehaberry

In response to this:

Bug 2167304: security: run the crash collector as ceph user

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: nehaberry.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@subhamkrai: This pull request references Bugzilla bug 2167304, which is valid.

2 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @nehaberry

In response to this:

Bug 2167304: security: run the crash collector as ceph user

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[subhamkrai]

What BZ is this for? We need Bug *: in the PR title

sorry, Travis I missed the ping.

[travisn]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: subhamkrai, travisn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [travisn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@subhamkrai: All pull requests linked via external trackers have merged:

• red-hat-storage/rook#447

Bugzilla bug 2167304 has been moved to the MODIFIED state.

In response to this:

Bug 2167304: security: run the crash collector as ceph user

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.