ROX-28151: Prometheus registry per user token#15809
Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at 59ff74d. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #15809 +/- ##
==========================================
+ Coverage 48.66% 48.67% +0.01%
==========================================
Files 2676 2676
Lines 199776 199818 +42
==========================================
+ Hits 97216 97261 +45
+ Misses 94950 94946 -4
- Partials 7610 7611 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
9430e5c to
fe18a4b
Compare
fdc542a to
5f63d54
Compare
7dba6d0 to
4565760
Compare
5f63d54 to
8f83cd6
Compare
5f58398 to
680ac3e
Compare
8f83cd6 to
15ab479
Compare
d1e3217 to
19b236f
Compare
7058c8a to
924e8b3
Compare
19b236f to
bd20b8f
Compare
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
bd20b8f to
f76345c
Compare
|
/retest |
f76345c to
718e3ca
Compare
|
@parametalol: The following tests 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. |
718e3ca to
59ff74d
Compare
Description
Instantiate a dedicated Prometheus registry for serving custom metrics per token identity.
This allows for application of SAC to the exposed data.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Unit tests.
Current dependencies on/for this PR: