Open jaronoff97 opened 5 months ago
it would also be great if the target-allocators per-node strategy said which job was lacking the node metadata info for the per-node strategy!
Hi @jaronoff97, I would like work on this issue. Can you please assign this to me ?
@parambath92 sure! let me know if you need any assistance in getting started!
@parambath92 do you have an ETA on when you can get this done? I'd like to be able to override the default target allocator endpoint with "target_allocator" config in prometheus receiver.
Hi @yingsamsung , I can work on it this weekend and update here.
Thank you so much. @parambath92
Just want to clarify, with your fix, I can override the default target_allocator.endpoint, hardcoded at here , right? Do you happen to know if there is any other way to set my own target allocator endpoint to, for example: otel-collector-targetallocator.my-namespace.svc.my-region.my-environment.cluster.local?
@yingsamsung i believe your issue is covered in #3242. This issue is in relation to not being able to set solely a target allocator configuration.
Component(s)
target allocator
What happened?
Description
The target allocator is supposed to be able accept only the target_allocator configuration, but right now it errors when doing so.
Steps to Reproduce
Create a collector with the target_allocator section set:
Expected Result
✅
Actual Result
Kubernetes Version
1.29.0
Operator version
0.100.1
Collector version
0.101.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
Log output
No response
Additional context
No response