-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
feat: add keep_dropped_targets limit to CRDs #5897
feat: add keep_dropped_targets limit to CRDs #5897
Conversation
21c3fea
to
cf90df4
Compare
cf90df4
to
4dcfa34
Compare
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.
Just some nits about comments and testing... definitely non-blocking
4dcfa34
to
0665ea5
Compare
@simonpasquier updated with changes |
0665ea5
to
4633080
Compare
Fixes prometheus-operator#5875 Signed-off-by: Jayapriya Pai <slashpai9@gmail.com>
4633080
to
d7622cd
Compare
Fixed the test, I dont remember why int was used for limits in tests in past. I updated to use uint64 since thats the type anyways. Also removed redundant tests. I will create separate PR for other limit tests. |
Fixes #5875
Description
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Adds keep_dropped_targets limit to CRDs at global as well as scrape level. Also added enforced fields
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
x
in the box that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.