Goal

• The goal of this epic is to adjust HighOverallControlPlaneCPU alert thresholds when Workload Partitioning is enabled.

Why is this important?

• On SNO clusters this might lead to false positives. Also, it makes sense to have such mechanism because right now it's using all available CPU for control plane alert, while user can allow less cores for it to be used

Scenarios

1. As a user i want to enable workload partitioning and have my alert values adjusted accordingly

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement
• ...

Open questions:

1. Do we want to bump alert threshold for SNO clusters because they are running workloads on master nodes, rather than worker nodes

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>