Repository navigation
ROX-37581: issue Sensor-bound metrics tokens from managed role - #23443
parametalol wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
Request: 'mapping on the sensor side: path->role, and allow managing permissions for this new role for sensor scrape requests on the central side'; 'users will have to explicitly configure the permissions according to the selected metrics needs.' A fixed metrics role request takes read permissions from Central's managed role, rejects client-supplied scopes and write grants, and binds the token to the verified Sensor cluster. Console token requests retain their existing policy. Also seed the role on non-OpenShift Central instances managing OpenShift secured clusters. AI-assisted: code partially generated by AI.
f66eb25 to
28f4fb2
Compare
|
Opened against the wrong stack layer for the requested role-description change. Moved the change to the secured-cluster role branch and opened #23444 instead. |
🚀 Build Images ReadyImages are ready for commit 28f4fb2. To use with deploy scripts: export MAIN_IMAGE_TAG=5.1.x-291-g28f4fb2fc6 |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## michael/ROX-37581-secured-cluster-metrics-role #23443 +/- ##
===============================================================================
Coverage 51.94% 51.95%
===============================================================================
Files 2914 2914
Lines 183665 183700 +35
===============================================================================
+ Hits 95408 95443 +35
Misses 79888 79888
Partials 8369 8369
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Description
Allow Sensor-proxied OpenShift Prometheus requests to use read permissions from the Central-managed secured-cluster metrics role, scoped to the authenticated Sensor's cluster. Reject caller-supplied permissions/scopes and write grants. This keeps permissions configurable without allowing the caller to choose a cluster or broader access; unlike the alternative of hard-coded scrape permissions, operators can select the read resources they need.
User-facing documentation
Testing and quality
Automated testing
How I validated my change