You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Jaeger Operator, I want the ability to set a custom cluster IP for the Jaeger Collector service so that I can tailor the networking configuration to specific requirements.
Problem
I need to create a custom internal DNS record that directs traffic to the Jaeger Collector service running on OTLP port 4317. This will allow efficient communication within the cluster and enable seamless trace data collection. By configuring a custom DNS record, we can simplify service discovery and ensure that other components within the system can reliably connect to the Jaeger Collector using its designated cluster IP and port.
Proposal
Currently, the Jaeger Operator deploys the Jaeger Collector service without allowing users to specify a custom cluster IP. It would be beneficial to have the ability to configure the cluster IP for the Jaeger Collector service directly through the operator. This feature enhancement would improve flexibility and allow users to tailor the Jaeger deployment to their specific networking requirements.
Proposed Solution
Modify Jaeger Custom Resource (CR): Extend the Jaeger Custom Resource (CR) definition to include an optional field for specifying the desired cluster IP for the Collector service.
Jaeger Operator Implementation:
When creating or updating a Jaeger instance, the operator should check if a custom cluster IP is provided in the CR.
If a cluster IP is specified, the operator should configure the Collector service accordingly.
If no cluster IP is provided, the operator can continue with the default behavior.
Documentation Update:
Update the official Jaeger Operator documentation to include details on how to set the cluster IP for the Collector service.
As part of improving the Jaeger Operator, I propose extending the ability to set custom cluster IP addresses beyond just the Collector service. Users should be able to configure the ClusterIP for other Jaeger components as well, such as the Query service.
The text was updated successfully, but these errors were encountered:
Requirement
As a Jaeger Operator, I want the ability to set a custom cluster IP for the Jaeger Collector service so that I can tailor the networking configuration to specific requirements.
Problem
I need to create a custom internal DNS record that directs traffic to the Jaeger Collector service running on OTLP port 4317. This will allow efficient communication within the cluster and enable seamless trace data collection. By configuring a custom DNS record, we can simplify service discovery and ensure that other components within the system can reliably connect to the Jaeger Collector using its designated cluster IP and port.
Proposal
Currently, the Jaeger Operator deploys the Jaeger Collector service without allowing users to specify a custom cluster IP. It would be beneficial to have the ability to configure the cluster IP for the Jaeger Collector service directly through the operator. This feature enhancement would improve flexibility and allow users to tailor the Jaeger deployment to their specific networking requirements.
Proposed Solution
Modify Jaeger Custom Resource (CR): Extend the Jaeger Custom Resource (CR) definition to include an optional field for specifying the desired cluster IP for the Collector service.
Jaeger Operator Implementation:
When creating or updating a Jaeger instance, the operator should check if a custom cluster IP is provided in the CR.
If a cluster IP is specified, the operator should configure the Collector service accordingly.
If no cluster IP is provided, the operator can continue with the default behavior.
Documentation Update:
Update the official Jaeger Operator documentation to include details on how to set the cluster IP for the Collector service.
Example Usage
Open questions
As part of improving the Jaeger Operator, I propose extending the ability to set custom cluster IP addresses beyond just the Collector service. Users should be able to configure the ClusterIP for other Jaeger components as well, such as the Query service.
The text was updated successfully, but these errors were encountered: