Use explicit roles/clusterroles for api-resource-collector #253
Conversation
The OLM doesn't allow us to use pre-existing roles/clusterroles, nor use aggregated roles either. So we need to define the roles explicitly. See: operator-framework/operator-lifecycle-manager#732
openshift-ci-robot
added
the
approved
|
Since this is blocking the release, I'm going to lgtm the PR so that we can do the release, Ozz showed me the result in a tmate session. We can iterate on the patch later. /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JAORMX, jhrozek 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:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
…cleanup Fix test log about --skip-cleanup-error
The OLM doesn't allow us to use pre-existing roles/clusterroles, nor
use aggregated roles either. So we need to define the roles explicitly.
See: operator-framework/operator-lifecycle-manager#732