-
Notifications
You must be signed in to change notification settings - Fork 525
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
Add Target Allocator/Stateful Set Option #310
Comments
/cc @Allex1 |
@blakeromano thanks for the heads up. |
I am not suggesting that you have to use the CRD. The CRD happens to allow the option to start up a pod that uses the collector's prometheus configuration and spins up a pod to do that work. I'd like to see the Helm Chart also have that functionality. Maybe a new helm chart to combine to Collector and Operator into one helm chart? |
@blakeromano is this issue related: #69 |
Related yes. I think there is a benefit to having a helm chart that would do both the operator and collector without the usage of the CRD. |
The CRD for the collector allows for the creation of the target allocator for prometheus which uses some of the data from the config on the collector regarding prometheus. However the Helm Chart has not added that support as well. This should be done to add awareness and adoption of the Target Allocator especially since lots of work on the Prometheus/Opentelemetry work has been going on
The text was updated successfully, but these errors were encountered: