-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[TEP-0124] implement opentelemetry Jaeger tracing #5746
Conversation
Hi @kmjayadeep. Thanks for your PR. I'm waiting for a tektoncd 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. |
/kind feature |
/ok-to-test |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
From the error in the build tests it might be that something went wrong in the rebase again, but you could try and run the codegen script to see if it fixes the error |
Hi @afrittoli I tried the codegen script already. It has introduced some formatting changes, but didn't fix the build. |
I had a look and your commit actually includes formatting changes to generated files, which causes the build job to fail.
I tried reverting those and running the codegen again and they appear back, so I suspect this might be related to a change in go version between CI and your/mine local go version. My go version is:
while CI runs on 1.18. For this specific CI, I would recommend reverting those changes and adding them to your commit. You can skip the codegen script since there is no change in the PR which requires it:
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Signed-off-by: Jayadeep KM <kmjayadeep@gmail.com>
Signed-off-by: Jayadeep KM <kmjayadeep@gmail.com>
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
and fix a few linter issues. Signed-off-by: Andrea Frittoli <andrea.frittoli@uk.ibm.com>
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
</tr><tr><td><p>"TaskRunResultLargerThanAllowedLimit"</p></td> | ||
<td><p>TaskRunReasonResultLargerThanAllowedLimit is the reason set when one of the results exceeds its maximum allowed limit of 1 KB</p> | ||
</td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like these were missed in some previous PR, but I wonder by CI did not catch them.
@vdemeester @abayer any idea?
Supported formats differ based on the KMS system used. | ||
One example of a KMS url could be: | ||
gcpkms://projects/[PROJECT]/locations/[LOCATION]>/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[KEY_VERSION] | ||
For more examples please refer <a href="https://docs.sigstore.dev/cosign/kms_support">https://docs.sigstore.dev/cosign/kms_support</a>. | ||
Note that the KMS is not supported yet.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
spanContext := make(map[string]string) | ||
|
||
// SpanContext was propogated through annotations | ||
if pr.Annotations != nil && pr.Annotations[SpanContextAnnotation] != "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! These means that a PipelineRun
too can receive an input context, which means we can support existing contexts for pipelines, like in the case of pipeline in pipeline, or a pipeline triggered via CloudEvent with a tracing context in it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @kmjayadeep
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
Adds opentelemetry instrumentation code to pipelinerun and taskrun reconcilers. Also made required changes in the main.go to include jaeger as tracing backend
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepNote to reviewers: There are pipeline failures (looks like they are not related to the changes). Once the review is complete and ready to approve, I will address the pipeline issues, rebase with main and squash all commits into one.
Release Notes