This is a clone of issue OCPBUGS-19828. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-19737. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-19512. The following is the description of the original issue:
—
OCPBUGS-5469 and backports began prioritizing later target releases, but we still wait 10m between different PromQL evaluations while evaluating conditional update risks. This ticket is tracking work to speed up cache warming, and allows changes that are too invasive to be worth backporting.
Definition of done:
- When presented with new risks, the CVO will initially evaluate one PromQL expression every second or so, instead of waiting 10m between different evaluations. Each PromQL expression will still only be evaluated once every hour or so, to avoid excessive load on the PromQL engine.
Acceptance Criteria:
- After changing the channel and receiving a new graph conditional risks are evaluated as quickly as possible, ideally less than 500ms per unique risk
- clones
-
OCPBUGS-19828 Faster risk cache warming
- Closed
- is blocked by
-
OCPBUGS-19828 Faster risk cache warming
- Closed
-
OCPBUGS-20263 Avoid panicking on all-fresh-cache evaluation
- Closed
- links to
-
RHBA-2023:6842 OpenShift Container Platform 4.12.z bug fix update