Skip to content
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

[Feature]: Set Cluster IP for Jaeger Collector Service #2547

Open
viktordienes opened this issue Apr 23, 2024 · 0 comments
Open

[Feature]: Set Cluster IP for Jaeger Collector Service #2547

viktordienes opened this issue Apr 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@viktordienes
Copy link

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

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: my-jaeger-instance
spec:
  # Other Jaeger configuration...
  collector:
    clusterIP: 10.0.0.100

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.

@viktordienes viktordienes added the enhancement New feature or request label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant