-
Notifications
You must be signed in to change notification settings - Fork 3.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
update code #6790
base: master
Are you sure you want to change the base?
update code #6790
Conversation
Signed-off-by: Swathi Enugula <Swathi.Enugula@fmr.com>
Welcome @SwathiEnugula202! |
Hi @SwathiEnugula202. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: SwathiEnugula202 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hey @SwathiEnugula202 |
The reason to bump the otelhttp version from v0.35.1 to v0.44.0 is related to a security vulnerability. Specifically, in v0.44.0, otel has fixed a CVE (Common Vulnerabilities and Exposures) in the otelhttp module1. This update ensures that the latest version of the otelhttp module is pulled by Kubernetes (k/k), which is essential for maintaining security and stability. |
Given that this change is for the e2e tests, it doesn't seem like there is really a problem. |
I believe the vendor directory needs to be updated per the test failure here. Can you please update? |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: