-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Allow enabling/disabling opentracing for ingresses #4732
Allow enabling/disabling opentracing for ingresses #4732
Conversation
Hi @willthames. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
Codecov Report
@@ Coverage Diff @@
## master #4732 +/- ##
==========================================
- Coverage 58.62% 58.61% -0.01%
==========================================
Files 88 89 +1
Lines 6743 6761 +18
==========================================
+ Hits 3953 3963 +10
- Misses 2353 2361 +8
Partials 437 437
Continue to review full report at Codecov.
|
@willthames please check the gofmt error
|
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.
Ensure that AWS and Docker credentials don't get accidentally added
1d0af54
to
6927d93
Compare
@aledbf that's done now, thanks! |
/lgtm |
@willthames thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf, willthames The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is a great feature - thanks for adding it :-) |
What this PR does / why we need it:
Occasionally you might want to enable opentracing only for a specific set of ingresses, or disable a specific ingress (this appears to be the easiest way to not trace specific paths such as an external healthcheck). While enabling opentracing is possible using location snippets, disabling opentracing is not currently possible (because
opentracing_propagate_context
cannot be unset once set).Special notes for your reviewer:
I would have liked the default for
enabled
to be the value forenable-opentracing
from the ConfigMap as that would have simplified a lot of logic (I wouldn't need theSet
property and the nginx template would have been more readable). I couldn't work out how to do that, but if it's possible, I would definitely be happy to refactor this change.