configuration-anomaly-detection
configuration-anomaly-detection copied to clipboard
PoC: k8s client usage for UWM down
https://issues.redhat.com/browse/OSD-23312
This PR showcases how CAD could use kube api with an example implementation of the remediation to https://issues.redhat.com/browse/OCPBUGS-33863.
The implementation is hidden behind a CAD_EXPERIMENTAL_ENABLED flag that we will enable on staging after enabling kube-api access in https://issues.redhat.com/browse/OSD-23311.
/hold this is an untested draft.
Codecov Report
Attention: Patch coverage is 18.51852% with 22 lines in your changes are missing coverage. Please review.
Project coverage is 37.85%. Comparing base (
61b1526) to head (b405fa7). Report is 2 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #279 +/- ##
==========================================
- Coverage 38.93% 37.85% -1.08%
==========================================
Files 17 19 +2
Lines 1500 1556 +56
==========================================
+ Hits 584 589 +5
- Misses 877 928 +51
Partials 39 39
| Files | Coverage Δ | |
|---|---|---|
| ...rrorbudgetburn/clustermonitoringerrorbudgetburn.go | 18.51% <18.51%> (ø) |
I was able to test this already thanks to backplane-cli using my ocm-token.
Waiting for this backplane api change, as we need to be able to pass our ocm connection for the backplane kube-api auth
/unhold
backplane-cli dependency PR merged. We're good to move ahead with this PR.
/hold
/unhold
Ready to merge! :)
Looks good! /lgtm
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: typeid, zmird-r
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [typeid,zmird-r]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@typeid: all tests passed!
Full PR test history. Your PR dashboard.
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 kubernetes-sigs/prow repository. I understand the commands that are listed here.