-
Notifications
You must be signed in to change notification settings - Fork 444
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
Change TargetAllocator configmap for ScrapeConfig and Probe CR #3469
base: main
Are you sure you want to change the base?
Change TargetAllocator configmap for ScrapeConfig and Probe CR #3469
Conversation
cc3c041
to
97b4885
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.
Looks good overall, some relatively minor nitpicks aside. Could you also add an e2e test for this behaviour? You can probably modify https://github.com/open-telemetry/opentelemetry-operator/tree/main/tests/e2e-targetallocator/targetallocator-prometheuscr.
53614ed
to
d673153
Compare
…TargetAllocatorPrometheusCR, create right configmap for target allocator Signed-off-by: qiyang <[email protected]>
d673153
to
d87da69
Compare
I'm not very familiar with E2E testing yet. I will take some time to look into it. |
d3861c1
to
4960f02
Compare
@swiatekm e2e test added |
Thanks for adding it! What you've added checks that setting the attribute on the CR leads to a change in the target allocator ConfgMap, which is a part of it. But since this PR effectively exposes this functionality to users, I'd like the new e2e test to also check that we actually allocate targets derived from ScrapeConfigs and Probes. What I'd like you to add is the following:
Does that make sense? For the record, the rest of your PR looks good to me. |
951c2a2
to
7ab7b88
Compare
Signed-off-by: qiyang <[email protected]>
5f4991f
to
19720d8
Compare
Signed-off-by: qiyang <[email protected]>
Signed-off-by: qiyang <[email protected]>
Signed-off-by: qiyang <[email protected]>
@dominicqi thanks for adding this :D I was planning on doing this when I got back from PTO but glad to see this is already here 🥳 With the changes that Mikolaj mentioned above this should be g2g. |
Description: Enable ScrapeConfigSelector and ProbeSelector support in OpenTelemetryTargetAllocatorPrometheusCR, create right configmap for target allocator
Link to tracking Issue(s):
Probe
andScrapeConfig
Prometheus Operator CRDs #1842Testing: add test in
configmap_test.go
Documentation: ScrapeConfigSelector and ProbeSelector config in v1beta1 api doc