question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Creation of TracingService requires restart of Ambassador to take effect

See original GitHub issue

Describe the bug

TracingService configuration is not applied until Ambassador is restarted.

To Reproduce

  1. Deploy Ambassador with service of type NodePort.
  2. Deploy Ambassador TracingService:
apiVersion: getambassador.io/v1
kind: TracingService
metadata:
  name: tracing
spec:
  service: jaeger:9411
  driver: zipkin
$ kubectl get tracingservices.getambassador.io

NAME      AGE
tracing   2m6s

Verify that tracing is now configured in the /ambassador/bootstrap-ads.json file:

"tracing": {
        "http": {
            "config": {
                "collector_cluster": "cluster_tracing_jaeger_9411",
                "collector_endpoint": "/api/v1/spans"
            },
            "name": "envoy.zipkin"
        }
    }
  1. Add a Ambassador Mapping to a test service:
apiVersion: getambassador.io/v1
kind: Mapping
metadata:
  name: test
spec:
  prefix: /test/
  rewrite: /
  service: test:80
  1. Hit Ambassador NodePort /test/... with traffic:
hey -c 5 -z 1m http://XXX.XXX.XXX.XXX:YYYY/test/some/api

...

Status code distribution:
  [200] 13690 responses

No tracing information is sent from the Ambassador to Jaeger. Watching tcpdump shows no packets from the Ambassador to Jaeger.

  1. Restart Ambassador pod:
kubectl delete pod ambassador-XXXXXXXXX-YYYY

Wait for the new pod to become up and running.

  1. Repeat step 4

Now (after restart) tracing information is properly delivered to Jaeger.

Expected behavior

Either creating TracingService should take effect immediately, or the fact that Ambassador has to be restarted after changing tracing configuration needs to be documented.

Versions:

  • Ambassador: 0.75.0
  • Kubernetes environment: Minikube
  • Version: 1.14.6

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6

github_iconTop GitHub Comments

1reaction
Pluiescommented, Jan 16, 2020

Ping @kflynn , is that something that could/should be looked into? Or is there a chance it’s already been fixed?

0reactions
stale[bot]commented, Mar 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Creation of TracingService requires restart of Ambassador to ...
Describe the bug TracingService configuration is not applied until Ambassador is restarted. To Reproduce Deploy Ambassador with service of ...
Read more >
Distributed tracing with Zipkin | Ambassador
Restarting Emissary-ingress is required after deploying a Tracing Service for changes to take effect. 2. Generate some requests. Use curl to generate a...
Read more >
An Intro to Ambassador - SFlanders
It was created because native Envoy configuration is hard to ... requires a restart of all impacted Ambassador pods to take effect.
Read more >
Ambassador tracing integration with Istio's Jaeger
The answer here is to install istio with --set values.global.tracer.zipkin.address as provided in istio documentation
Read more >
Distributed Tracing with Java “MicroDonuts”, Kubernetes and ...
Recently the Kubernetes-native Ambassador API gateway added ... There are two Ambassador annotations in this file: one TracingService to ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found