🐛 Use correct case on verb for metrics-viewer ClusterRole #3081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Some things take you much longer to find than you'd be willing to admit - This is one of them. I was trying to get metrics from
/metrics
with themetrics-viewer
user we added in #3064, and it just. wasn't. working. I banged my head against that wall for several days.Until I read the upstream documentation and realised the difference to our
ClusterRole
: The verb was all caps in ours. And - obviously, some might say - verbs in ClusterRoles are case-sensitive! SoGET
!=get
. This confusion is compounded by the fact that the HTTP verb, in fact, isGET
. Kubernetes still seems to expectget
here.Binding to this
ClusterRole
gave me two different outcomes depending on which verb I had in there:Related issue(s)
Fixes #
Release Notes