WIP: DPTP-2938: add configurable skip for authoritative decrease by workload type#5307
WIP: DPTP-2938: add configurable skip for authoritative decrease by workload type#5307deepsm007 wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@deepsm007: This pull request references DPTP-2938 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 story to target the "5.0.0" version, but no target version was set. 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. |
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (3)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deepsm007 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 |
0e2df30 to
dd8eb2c
Compare
|
@deepsm007: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Follow-up to DPTP-2938 / peak usage basis (#5306, merged). Adds configurable skip rules so authoritative resource decreases can be disabled for specific workload types or classes.
After authoritative rollout, image builds (OpenShift Build pods) were still at risk: peak basis fixes most burst cases, but limit decreases on
buildworkloads remain a safety concern for compile spikes. This change lets ops skip authoritative decreases selectively without turning off authoritative mode globally.openshift/release#81763
/cc @openshift/test-platform