Bump ksm to 2.8.2 #19559
Bump ksm to 2.8.2 #19559
Conversation
Go Package Import DifferencesBaseline: 23514b1
|
Bloop Bleep... Dogbot HereRegression Detector ResultsRun ID: 1c7b0d34-19d4-417c-8741-f695f28d2af8 ExplanationA regression test is an integrated performance test for Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval. We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:
The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed. No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%. Fine details of change detection per experiment.
|
What does this PR do?
This PR bumps ksm to 2.8.2.
Motivation
We want to keep the latest version available to benefit from all the fixes.
Additional Notes
We could not bump to 2.10.0 because of kubernetes/kube-state-metrics#2202.
2.8.2 contains @clamoriniere 's fix #15623 so it's good enough.
Possible Drawbacks / Trade-offs
N/A
Describe how to test/QA your changes
Deploy the Cluster-Agent on the oldest Kubernetes version possible with KSM enabled and all the optional metrics (
collectCrdMetrics,collectSecretMetrics... on the helm chart). Make sure all the different metrics are still collected. You'll need to create crd, jobs, cronjobs, secrets, hpa, vpa... of multiple versions.Reviewer's Checklist
Triagemilestone is set.major_changelabel if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changeloglabel has been applied.qa/skip-qalabel is not applied.team/..label has been applied, indicating the team(s) that should QA this change.need-change/operatorandneed-change/helmlabels have been applied.k8s/<min-version>label, indicating the lowest Kubernetes version compatible with this feature.