Add Prometheus jobs to fetch k8s resource metrics #2149
Merged
Conversation
This file contains hidden or 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
nghialv
reviewed
Jun 29, 2021
manifests/pipecd/values.yaml
Outdated
| regex: admin | ||
|
|
||
| # Scrape config for API servers. | ||
| - job_name: 'kubernetes-apiservers' |
Member
There was a problem hiding this comment.
nit: Remove ' to be unified with other jobs.
Member
Author
|
applied |
Member
|
Nice. |
Member
Author
|
/trigger test |
Collaborator
|
@nakabonne: Your requested test has been scheduled in response to this comment. |
Collaborator
|
Code coverage for golang is |
Member
|
Way to go 🚀 |
Collaborator
|
This pull request is APPROVED by Approvers can cancel the approval by writing |
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.
What this PR does / why we need it:
This PR adds three Prometheus jobs to retrieve resources metrics.
Which issue(s) this PR fixes:
Ref #1867
Does this PR introduce a user-facing change?: