cincinnati
cincinnati copied to clipboard
openshift
OTA-869: separate the cincinnati graph-builder and policy-engine deployments
Separate the Graph Builder and Policy Engine deployments so that we can scale up PE quickly instead of waiting for graph to refresh. PE will use graph from existing graph-builder to get the complete graph
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: PratikMahajan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [PratikMahajan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@PratikMahajan: This pull request references OTA-869 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.19.0" version, but no target version was set.
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 openshift-eng/jira-lifecycle-plugin repository.
@PratikMahajan: This pull request references OTA-869 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.19.0" version, but no target version was set.
In response to this:
Separate the Graph Builder and Policy Engine deployments so that we can scale up PE quickly instead of waiting for graph to refresh. PE will use graph from existing graph-builder to get the complete graph
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@PratikMahajan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e | 43bd033e1c8b2a928f5eef0a1ba809b01d36133a | link | true | /test e2e |
| ci/prow/customrust-e2e | 43bd033e1c8b2a928f5eef0a1ba809b01d36133a | link | true | /test customrust-e2e |
| ci/prow/verify-openapi | 43bd033e1c8b2a928f5eef0a1ba809b01d36133a | link | true | /test verify-openapi |
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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-sigs/prow repository.