This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
Add tracing options when Jaeger deployment is enabled for the demo script #3947
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Currently the demo script will deploy Jaeger if the
DEPLOY_JAEGER
env var is set. However, there is no logic to enableOpenServiceMesh.tracing.enable
and set the tracing endpoint. This PR introduces that so the script user doesn't have any other additional steps to enable the tracing component.Affected area:
Testing done:
Ran the demo script and observed the tracing.
Please answer the following questions with yes/no.
No.
No.