[release-4.22] OCPBUGS-107644: Bump OpenTelemetry dependencies to v1.44.0 to fix CVE-2026-41178

[amitesh1201]

Summary

• Bump go.opentelemetry.io/otel, otel/sdk, otel/trace, and otel/metric from v1.43.0 to v1.44.0
• Addresses CVE-2026-41178 (DoS via uncapped baggage header parsing in OpenTelemetry)

Test plan

• CI passes on openshift-4.22
• Verify go mod tidy is clean across server/, tests/, etcdutl/, and root modules

Made with Cursor

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-107644, which is invalid:

• expected dependent Jira Issue OCPBUGS-109478 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• Bump go.opentelemetry.io/otel, otel/sdk, otel/trace, and otel/metric from v1.43.0 to v1.44.0
• Addresses CVE-2026-41178 (DoS via uncapped baggage header parsing in OpenTelemetry)

Test plan

• CI passes on openshift-4.22
• Verify go mod tidy is clean across server/, tests/, etcdutl/, and root modules

Made with Cursor

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amitesh1201
Once this PR has been reviewed and has the lgtm label, please assign hasbro17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b4cd9684-9ac2-4899-806d-b47fc7e67e4c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[amitesh1201]

/jira refresh

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-107644, which is invalid:

• expected dependent Jira Issue OCPBUGS-109478 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[amitesh1201]

/retest

[amitesh1201]

/retest

[openshift-ci]

@amitesh1201: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/upstream-integration	268020f	link	false	/test upstream-integration
ci/prow/upstream-e2e	268020f	link	false	/test upstream-e2e

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.