Networking Examples¶

Configure ingress, load balancing, and network policies for Jaeger components.

Single Ingress¶

Route all traffic through one ingress controller.

collector-single-ingress-values.yaml

# Default values for jaeger.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

collector:
  install: true
  ingress:
    install: true
    host: jaeger-collector.test.org

Key parameters: - collector.ingress.grpc - gRPC endpoint for trace collection - collector.ingress.http - HTTP endpoint for trace collection - query.ingress.tls - TLS termination configuration - Annotations for NGINX ingress controller

Multiple Ingresses¶

Separate ingresses for different environments or teams.

collector-multiple-ingresses-values.yaml

# Default values for jaeger.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

collector:
  install: true
  ingress:
    install: true
    hosts:
    - host: zipkin.jaeger-collector.test.org
      paths:
      - prefix: /zipkin
        service:
          port: 9411
    - host: trift.jaeger-collector.test.org
      paths:
      - prefix: /thrift/tchannel
        service:
          port: 14250
      - prefix: /thrift/grpc
        service:
          port: 14267
      - prefix: /thrift/http
        service:
          port: 14268
    - host: otel.jaeger-collector.test.org
      paths:
      - prefix: /otlp/grpc
        service:
          port: 4317
      - prefix: /otlp/http
        service:
          port: 4318

Key parameters: - ingressClassName - Specific ingress controller - Rate limiting annotations - Authentication integration - Multiple ingress definitions

Custom Service Names¶

Use custom service names for better organization.

collector-custom-service-name-values.yaml

# Default values for jaeger.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

collector:
  install: true
  ingress:
    install: true
    hosts:
    - host: jaeger-collector.test.org
      paths:
      - prefix: /zipkin
        service:
          # The "name" parameter allow to set Service name that will use
          # By default will use Service name creating during Jaeger deploy
          # It usually has a name: jaeger-collector
          name: my-awesome-service-name
          port: 9411

Key parameters: - serviceName - Custom Kubernetes service name - servicePort - Specific port mapping - Consistent naming across components

Usage¶

Choose networking approach
Update hostnames and annotations
Configure TLS certificates if needed
Deploy with Helm:

helm install jaeger qubership-jaeger/qubership-jaeger -f networking-values.yaml