operator: add ingress and routes to related objects #210
Conversation
openshift-ci-robot
added
the
size/XS
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, mfojtik 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 |
openshift-ci-robot
added
the
approved
|
@mfojtik: cannot checkout 4.2: error checking out 4.2: exit status 1. output: error: pathspec '4.2' did not match any file(s) known to git. In 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 kubernetes/test-infra repository. |
|
/cherrypick release-4.2 |
|
@mfojtik: new pull request created: #217 In 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 kubernetes/test-infra repository. |
As we see more degraded operators because of broken routing, add ingress, route and service to related objects, so inspect will collect them. Adding the openshift-ingress namespace to related objects means the insights operator will copy out any failing pod in that namespace.