[Chore] Update otel components to v0.127.0/v0.121.0

[khushijain21]

What does this PR do?

It updates all otel components except prometheus-receiver due to its dependency on higher prometheus version (which conflicts with beats code). We should update prometheus-receiver once the following issue is resolved. See elastic/beats#42916

This is a temporary solution to unblock us with otel related work on main branch.

This update was performed using following command

.ci/scripts/otel-update.sh v0.121.0 v1.27.0 v0.121.0 

and manually degraded the version of prometheus-receiver.
Skipping changelog for now.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

How to test this PR locally

go build .
sudo ./elastic-agent otel

Related issues

• Supersedes [chore] Update prometheus to match OTel v0.120.0 beats#42748, Update OTel components to v0.120.x #7663

[mergify]

This pull request does not have a backport label. Could you fix it @khushijain21? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[khushijain21]

/test

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b updateotel upstream/updateotel
git merge upstream/main
git push upstream updateotel

[khushijain21]

/test

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[mauri870]

I tested this manually: elastic-agent compiles, the collector appears to work as before, and all tests pass. I think it's fine to merge this.

One concern is the prometheusreceiver. The collector compiles, but does it actually work with the different version of the receiver? I suppose the best way to be sure is to create a configuration using prometheusreceiver and confirm that it works.

[khushijain21]

One concern is the prometheusreceiver. The collector compiles, but does it actually work with the different version of the receiver? I suppose the best way to be sure is to create a configuration using prometheusreceiver and confirm that it works.

Well, one reason I wouldn't want to test it out - is because this is a temporary solution (to unblock us). We should soon be able to ramp the prometheus-receiver version and any concerns regarding version compatibility can rest

[pkoutsovasilis]

@khushijain21 @mauri870 what backports we need here?

[mauri870]

@khushijain21 @mauri870 what backports we need here?

Based on the original PR, only 8.x which I just added.

[cmacknz]

Skipping changelog for now.

I think there should be a changelog for the bump to otel 0.121.0. There are tons of changes included in upstream releases so we shouldn't silently do these version bumps.

[cmacknz]

Thanks for the updates!

[khushijain21]

/test

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8630ca3

History

• 💔 Build #19639 failed 8630ca3
• 💚 Build #19623 succeeded 5528e62
• 💛 Build #19597 was flaky 63e705d
• 💔 Build #19587 failed 488a088
• 💔 Build #19586 failed 488a088

cc @khushijain21