add nginx-plus-module-otel to base image

[justdan96]

Proposed changes

This PR is just to add nginx-plus-module-otel to the base images, so that OpenTelemetry can be configured easily.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[jjngx]

Hi @justdan96, thank you for opening the PR. Please follow the project contributing guideline described here.

[brianehlert]

This could benefit from:

• an Issue that describes the enhancement (this informs release notes and watchers)
• at least an example showing other users how to use the module

[justdan96]

an Issue that describes the enhancement (this informs release notes and watchers)

There isn't a lot to describe, this just avoids users having to compile their own images to add the otel module (or use a custom init container).

at least an example showing other users how to use the module

It currently isn't possible to use the module (even with this merged) as it needs to be enabled in the template. It would need code similar to that for OpenTracing - i.e.: https://github.com/nginxinc/kubernetes-ingress/blob/2641fbb237352112912e2698994015286863d21b/internal/configs/config_params.go#L32
I don't have time to do that at the moment so this PR is just the first step. Users can otherwise refer to this page for module configuration parameters: https://docs.nginx.com/nginx/admin-guide/dynamic-modules/opentelemetry/.

[brianehlert]

The key question that we need an answer for before accepting this PR is:

• can both the OpenTracing and OpenTelemetry modules be installed at the same time and not interact in a negative way with each other?

This is so we can give a path for customers to migrate from OpenTracing to OpenTelemetry Tracing in-place and not introduce an immediately breaking change.
We totally embrace moving to the new native NGINX OpenTelemetry module but want to be sure to also do the right thing for anyone using OpenTracing and not introduce a release that immediately breaks them if we can avoid it.

Can anyone / has anyone investigated this?

[brianehlert]

Also, the NGINX OpenTelemetry module should be an option for both NGINX Plus and NGINX open source.

[justdan96]

1. We have both modules installed at the same time with no ill effects. We have only one loaded though.
2. I can amend the Dockerfile to add it to further images.

[brianehlert]

Since this will be configured exclusively using snippets at this time, it would be great if there was also an example included.
Probably under /shared-examples (not entirely sure though)
That could help us cover a documentation gap.

[justdan96]

Actually for point 2 there doesn't seem to be Docker images I could copy the .so files from, so I am assuming we would want to compile from source?

[brianehlert]

I think the key here is that we need a solution for this for both the free and N+ releases.

[defanator]

• can both the OpenTracing and OpenTelemetry modules be installed at the same time and not interact in a negative way with each other?

I believe they can, there's nothing that should prevent having both and using just the one. I'm tagging @dplotnikov-f5 and @thresheek as they could share first-hand feedback.

[brianehlert]

If we can finish this with the N+ OTEL module that is fine.
While any N OSS module sorts itself out.

[github-actions]

This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This PR was closed because it has been stalled for 10 days with no activity.

[justdan96]

I need to look at this again at some point.