-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Configure OpenTelemetry Tracing #4883
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
Conversation
Hi @sallyom. Thanks for your PR. I'm waiting for a cri-o 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. |
14900e1
to
19373b3
Compare
/cc @fidencio Is the replacement for grpc version still required? I hope not! |
/ok-to-test |
Hmm. I think it still is, I'm afraid. |
/cc @fgiudici, would you have time to check this out? What's the status of your PR on containerd side? |
The patch (containerd/ttrpc#67 ) hasn't been merged as containerd folks prefer to switch the gogo protobuf to the google protobuf. That would be the future proof fix (as gogo protobuf is no more supported). |
I just tested this PR and I see absolutely no issue on starting a pod using kata-containers. |
I have to take some time to look at the code to recall how exactly the issue happened. I can do that tomorrow. |
/retest |
kata-containers CI is failing due to:
|
fd01f31
to
1baa3ad
Compare
/test critest_fedora |
@haircommander ptal and thank you! |
/retest-required |
@haircommander @saschagrunert all tests are green, also, I added |
the PR generally looks good to me. I would love if we could have some tests showing how this all works e2e in cri-o. The integration suite in test/ directory is a good place I think, though, without support in crictl, is that even possible? If not, I think it would also be helpful to have some documentation about how to configure everything e2e. That could live in the tutorials/ directory. Both/either/neither can be done as follow ups though /approve Thanks for all your hard work 🙂 |
@haircommander, I do have tutorials/docs/video of all this working, I will definitely have a follow-up PR coming w/in the next few days to show how to enable & collect. |
Signed-off-by: Sally O'Malley <[email protected]> Co-authored-by: husky-parul <[email protected]>
Signed-off-by: Sally O'Malley <[email protected]>
Signed-off-by: Sally O'Malley <[email protected]>
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, sallyom, saschagrunert 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 |
/retest-required |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@sallyom: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/retest-required |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR configures opentelemetry tracer provider and exporter and adds initial spans.
This PR follows the example of etcd & kube-apiserver
etcd: etcd-io/etcd#12919
kube-apiserver: kubernetes/kubernetes#94942
Which issue(s) this PR fixes:
#4734
Does this PR introduce a user-facing change?