🐛 disable keycloak servicemonitor #416
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
|
/lgtm |
jmontleon
force-pushed
the
disable-keycloak-servicemonitor
branch
from
900f6ac to
5980e21
Compare
jmontleon
changed the title
|
/lgtm |
Signed-off-by: Jason Montleon <[email protected]>
jmontleon
force-pushed
the
disable-keycloak-servicemonitor
branch
from
5980e21 to
3f3c265
Compare
|
/lgtm |
This was referenced Mar 26, 2025
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.
The reason for this is that there is a bug that causes the metrics/monitoring target to be broken and return a 404. Disabling it and cleaning up the servicemonitor is the best we can do to stop the noise right now. With RHBK there is no servicemonitor installed so nothing to do there.
https://issues.redhat.com/browse/RHSSO-1960