Bug 2180685:[release-4.12] Add/update securityContext for containers

[openshift-cherrypick-robot]

This is an automated cherry-pick of #290

/assign SanjalKatiyar

[SanjalKatiyar]

/retitle Bug 2180685: [release-4.12] Add/update securityContext for containers

[openshift-ci]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2180685, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (ODF 4.12.3) matches configured target release for branch (ODF 4.12.3)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (ebenahar@redhat.com), skipping review request.

In response to this:

Bug 2180685: [release-4.12] Add/update securityContext for containers

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.

[SanjalKatiyar]

cc @iamniting @agarwal-mudit

[iamniting]

/override ci/prow/odf-operator-bundle-e2e-aws

[openshift-ci]

@iamniting: Overrode contexts on behalf of iamniting: ci/prow/odf-operator-bundle-e2e-aws

In response to this:

/override ci/prow/odf-operator-bundle-e2e-aws

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, openshift-cherrypick-robot

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 [iamniting]

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

[openshift-ci]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

• red-hat-storage/odf-operator#287
• red-hat-storage/odf-operator#290
• red-hat-storage/odf-operator#314

Bugzilla bug 2180685 has been moved to the MODIFIED state.

In response to this:

Bug 2180685:[release-4.12] Add/update securityContext for containers

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.

[SanjalKatiyar]

/cherry-pick release-4.10

[SanjalKatiyar]

/cherry-pick release-4.11

[openshift-cherrypick-robot]

@SanjalKatiyar: #314 failed to apply on top of branch "release-4.10":

Applying: bundle: update capabilities for all containers
Using index info to reconstruct a base tree...
M	bundle/manifests/odf-operator.clusterserviceversion.yaml
M	config/console/console_init.yaml
M	config/default/manager_auth_proxy_patch.yaml
M	config/default/manager_webhook_patch.yaml
M	config/manager/manager.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manager/manager.yaml
CONFLICT (content): Merge conflict in config/manager/manager.yaml
Auto-merging config/default/manager_webhook_patch.yaml
CONFLICT (content): Merge conflict in config/default/manager_webhook_patch.yaml
Auto-merging config/default/manager_auth_proxy_patch.yaml
CONFLICT (content): Merge conflict in config/default/manager_auth_proxy_patch.yaml
Auto-merging config/console/console_init.yaml
CONFLICT (content): Merge conflict in config/console/console_init.yaml
Auto-merging bundle/manifests/odf-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/odf-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 bundle: update capabilities for all containers
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.10

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-cherrypick-robot]

@SanjalKatiyar: #314 failed to apply on top of branch "release-4.11":

Applying: bundle: update capabilities for all containers
Using index info to reconstruct a base tree...
M	bundle/manifests/odf-operator.clusterserviceversion.yaml
M	config/console/console_init.yaml
M	config/default/manager_auth_proxy_patch.yaml
M	config/default/manager_webhook_patch.yaml
M	config/manager/manager.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manager/manager.yaml
CONFLICT (content): Merge conflict in config/manager/manager.yaml
Auto-merging config/default/manager_webhook_patch.yaml
CONFLICT (content): Merge conflict in config/default/manager_webhook_patch.yaml
Auto-merging config/default/manager_auth_proxy_patch.yaml
CONFLICT (content): Merge conflict in config/default/manager_auth_proxy_patch.yaml
Auto-merging config/console/console_init.yaml
CONFLICT (content): Merge conflict in config/console/console_init.yaml
Auto-merging bundle/manifests/odf-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/odf-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 bundle: update capabilities for all containers
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.11

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.