![]() By default you might want opentracing off, but on for a particular ingress. Similarly, you might want opentracing globally on, but disabled for a specific endpoint. To achieve this, `opentracing_propagate_context` cannot be set when combined with `opentracing off` A new annotation, `enable-opentracing` allows more fine grained control of opentracing for specific ingresses. |
||
---|---|---|
.. | ||
deploy | ||
enhancements | ||
examples | ||
images | ||
user-guide | ||
development.md | ||
extra.css | ||
how-it-works.md | ||
index.md | ||
kubectl-plugin.md | ||
troubleshooting.md |