New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MON-1708: Enforce label scrape limits in UWM #1350
MON-1708: Enforce label scrape limits in UWM #1350
Conversation
bba96da
to
3ac21fc
Compare
@dgrisonnet @simonpasquier I have created #1374 to update dependencies. Once that is merged I will remove the conflicting commits from this PR |
46e9b3a
to
870a839
Compare
@dgrisonnet I updated the PR after syncing dependencies in another PR. Also added assertion |
870a839
to
2049d5e
Compare
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me so far, but let's also look into setting sane defaults in this PR.
/retest-required |
2049d5e
to
3ed6d2c
Compare
This PR was on hold till we get the changes to downstream which removed a label with a large label value in kubelet metric. We thought of initially enforcing limits in platform monitoring first and then proceed with uwm but starting with UWM looks to be good since we will already the metrics we are using incase of platform monitoring and we can enforce values in there after testing a little bit more since scrape can fail if we set a lower value for label limits |
3ed6d2c
to
18a4876
Compare
cc: @simonpasquier |
1588397
to
ecf0e02
Compare
alert is already here cluster-monitoring-operator/assets/prometheus-k8s/prometheus-rule.yaml Lines 226 to 237 in 7395939
|
d2e007c
to
7b2815e
Compare
/lgtm |
/lgtm |
/skip |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/hold till docs approved on epic |
This commit adds feature to support label scrape limits in user workload monitoring by allowing cluster admin set enforcedLabelLimit, enforcedLabelNameLengthLimit and enforcedLabelValueLengthLimit in config map Signed-off-by: Jayapriya Pai <janantha@redhat.com>
7b2815e
to
e6f53b8
Compare
/unhold since docs-approved on epic https://issues.redhat.com/browse/MON-2195 @jan--f /@arajkumar Can you review again, I had to rebase due to changelog conflict |
/retest |
2 similar comments
/retest |
/retest |
@slashpai: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arajkumar, jan--f, raptorsun, simonpasquier, slashpai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
MON-1708 -> Enforce label scrape limits. This feature is available in prometheus-operator 0.50 only