-
Epic
-
Resolution: Done
-
Undefined
-
None
-
Allow the config-policy-controller QPS to be configurable
-
False
-
None
-
False
-
Yellow
-
To Do
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
<https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
Epic Template descriptions and documentation.
<https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
ACM-wide Product Requirements (Top-level Epics)
<https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
As a heavy user of Configuration Policies, I would like the Configuration Policy controller's allowed Kubernetes API queries per second (QPS) to scale with the number of evaluation concurrency I set.
Right now, the controller is only has a default QPS of 5. This should be at least 15 per evaluation goroutine, which is set by the evaluation concurrency setting. The value 15 should be configurable on the ManagedClusterAddOn object.
Why is this important?
Performance is an issue when there are many configuration policies.
Scenarios
N/A
Acceptance Criteria
- The config-policy-controller QPS default is changed to 15 * evaluation concurrency.
- The config-policy-controller QPS is configurable per cluster.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release 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>
ACM Epic Done Checklist
See presentation and details.
Update with "Y" if Epic meets the requirement, "N" if it does not, or "N/A" if not applicable.
- N/A FIPS Readiness
- N/A Works in Disconnected
- N/A Global Proxy Support
- N/A Installable to Infrastructure Nodes
- N/A No impacts to Performance and Scalability
- N/A Backup and Restorable