Add kube-rbac-proxy to content-service #11782
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ArthurSens <arthursens2005@gmail.com>
aledbf
approved these changes
Aug 1, 2022
roboquat
added
deployed: workspace
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: ArthurSens arthursens2005@gmail.com
Description
Recently we added a new alert for whenever Prometheus fails to scrape a component, and we immediately got alerted about content-service being unreachable. After some debugging, we traced down #11591 which introduced a breaking change for many
/metricsendpoints.This PR adds kube-rbac-proxy to content-service, which will make the metrics endpoint reachable again.
Related Issue(s)
Resolves alerts such as this one.
How to test
Release Notes
Werft options: