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

TracingService: propagation_modes incompatible with opentelemetry driver #5505

Open
miguelvr opened this issue Jan 10, 2024 · 0 comments
Open

Comments

@miguelvr
Copy link

Describe the bug
Emissary ingress pod enters CrashLoopBackoff when propagation_modes is specified with driver: opentelemetry.

Also, the documentation hints that the way to specify propagation modes is spec.propagation_modes, when in reality it is spec.config.propagation_modes.

To Reproduce

  1. Apply the following TracingService:
apiVersion: getambassador.io/v3alpha1
kind: TracingService
metadata:
  name: tracing
  namespace: emissary
spec:
  driver: opentelemetry
  service: opentelemetry-collector.opentelemetry:4317
  config:
    service_name: emissary
    propagation_modes: [TRACE_CONTEXT]
  sampling:
    overall: 100
  1. Restart emissary-ingress deployment
  2. Observe the CrashLoopBackOff

Expected behavior

  • propagation_modes to be supported with opentelemetry driver
  • emissary-ingress pod to restart successfully

Versions (please complete the following information):

  • Ambassador: v3.9.1
  • Kubernetes environment: Google Kubernetes Engine
  • Version: v1.25.13-gke.20
@miguelvr miguelvr changed the title propagation_modes incompatible with opentelemetry driver TracingService: propagation_modes incompatible with opentelemetry driver Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant