OCPBUGS-65497: Add ClusterRole to ClusterOperator relatedObjects#373
OCPBUGS-65497: Add ClusterRole to ClusterOperator relatedObjects#373RadekManak wants to merge 1 commit intoopenshift:mainfrom
Conversation
This adds the control-plane-machine-set-operator ClusterRole to the ClusterOperator's relatedObjects to ensure it's collected by oc adm inspect and must-gather for debugging purposes. The name field is set to the specific ClusterRole name since the operator manages a single ClusterRole resource.
|
@RadekManak: This pull request references Jira Issue OCPBUGS-65497, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@RadekManak: This pull request references Jira Issue OCPBUGS-65497, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
This adds the control-plane-machine-set-operator ClusterRole to the ClusterOperator's relatedObjects to ensure it's collected by oc adm inspect and must-gather for debugging purposes.
The name field is set to the specific ClusterRole name since the operator manages a single ClusterRole resource.