OpenTelemetry static linking

[esigo]

What this PR does / why we need it:

This PR statically links OpenTelemetry dependencies to reduce the number and the size of the files stored in the side-car container.
The size of container image is reduced from ~50 to ~17 MB.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

related to #9016

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.
• Added Release Notes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

OpenTelemetry static linking

[k8s-ci-robot]

Hi @esigo. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[strongjz]

/ok-to-test

/triage accepted
/priority backlog
/kind feature

[rikatz]

/lgtm
/approve
Thank you!

[rikatz]

/hold

[rikatz]

Just a question before merging, will this work with our current v1.21 version? How can we keep this in sync?

Otherwise feel free to unhold :)

[strongjz]

@rikatz I dropped 1.21 from the supported table and removed it from e2e since 1.21 was EOL last month.

[rikatz]

Sorry nginx v1.21, not k8s

[esigo]

Sorry nginx v1.21, not k8s

@rikatz thanks. 1.21 should work with my last commit. I'll test tomorrow.

[esigo]

@rikatz tested with nginx 1.21:

[rikatz]

Pardon my ignorance, but this errors in the end of the log are something concerning?

[esigo]

Pardon my ignorance, but this errors in the end of the log are something concerning?

Here I was able to load the module and the errors mean the collector/backend is not reachable. So I could produce traces but I send them to an address that does not exist and hence the errors. #9062 should be merged in order to configure the collector correctly.

[rikatz]

Thanks!
/unhold

[rikatz]

/lgtm
Thank you

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: esigo, rikatz

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:

• images/OWNERS [rikatz]

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