chore(deps): bump github.com/open-telemetry/opentelemetry-operator from 0.103.0 to 0.110.0 in /tests

[dependabot]

Bumps github.com/open-telemetry/opentelemetry-operator from 0.103.0 to 0.110.0.

Release notes

Sourced from github.com/open-telemetry/opentelemetry-operator's releases.

Release v0.110.0

0.110.0

🛑 Breaking changes 🛑

• auto-instrumentation: Enable multi instrumentation by default. (#3090)

  Starting with this release, the OpenTelemetry Operator now enables multi-instrumentation by default. This enhancement allows instrumentation of multiple containers in a pod with language-specific configurations.

  Key Changes:

  • Single Instrumentation (Default Behavior): If no container names are specified using the instrumentation.opentelemetry.io/container-names annotation, instrumentation will be applied to the first container in the pod spec by default. This only applies when single instrumentation injection is configured.
  • Multi-Container Pods: In scenarios where different containers in a pod use distinct technologies, users must specify the container(s) for instrumentation using language-specific annotations. Without this specification, the default behavior may not work as expected for multi-container environments.

  Compatibility:

  • Users already utilizing the instrumentation.opentelemetry.io/container-names annotation do not need to take any action. Their existing setup will continue to function as before.
  • Important: Users who attempt to configure both instrumentation.opentelemetry.io/container-names and language-specific annotations (for multi-instrumentation) simultaneously will encounter an error, as this configuration is not supported.

• collector: Remove ComponentUseLocalHostAsDefaultHost collector feature gate. (#3306)

  This change may break setups where receiver endpoints are not explicitly configured to listen on e.g. 0.0.0.0. Change #3333 attempts to address this issue for a known set of components. The operator performs the adjustment for the following receivers:

  • otlp
  • skywalking
  • jaeger
  • loki
  • opencensus
  • zipkin
  • tcplog
  • udplog
  • fluentforward
  • statsd
  • awsxray/UDP
  • carbon
  • collectd
  • sapm
  • signalfx
  • splunk_hec
  • wavefront

💡 Enhancements 💡

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-operator's changelog.

0.110.0

🛑 Breaking changes 🛑

• auto-instrumentation: Enable multi instrumentation by default. (#3090)

  Starting with this release, the OpenTelemetry Operator now enables multi-instrumentation by default. This enhancement allows instrumentation of multiple containers in a pod with language-specific configurations.

  Key Changes:

  • Single Instrumentation (Default Behavior): If no container names are specified using the instrumentation.opentelemetry.io/container-names annotation, instrumentation will be applied to the first container in the pod spec by default. This only applies when single instrumentation injection is configured.
  • Multi-Container Pods: In scenarios where different containers in a pod use distinct technologies, users must specify the container(s) for instrumentation using language-specific annotations. Without this specification, the default behavior may not work as expected for multi-container environments.

  Compatibility:

  • Users already utilizing the instrumentation.opentelemetry.io/container-names annotation do not need to take any action. Their existing setup will continue to function as before.
  • Important: Users who attempt to configure both instrumentation.opentelemetry.io/container-names and language-specific annotations (for multi-instrumentation) simultaneously will encounter an error, as this configuration is not supported.

• collector: Remove ComponentUseLocalHostAsDefaultHost collector feature gate. (#3306)

  This change may break setups where receiver endpoints are not explicitly configured to listen on e.g. 0.0.0.0. Change #3333 attempts to address this issue for a known set of components. The operator performs the adjustment for the following receivers:

  • otlp
  • skywalking
  • jaeger
  • loki
  • opencensus
  • zipkin
  • tcplog
  • udplog
  • fluentforward
  • statsd
  • awsxray/UDP
  • carbon
  • collectd
  • sapm
  • signalfx
  • splunk_hec
  • wavefront

💡 Enhancements 💡

• auto-instrumentation, collector: Add a must gather utility to help troubleshoot (#3149)

... (truncated)

Commits

• 65b40cb Prepare v0.110.0 release (#3336)
• 9f1eb13 internal/components: remove unused type (#3339)
• 7ee69c5 Fixes bug where we tried to default config for the wrong components (#3337)
• 098afda apis/v1beta1: remove ComponentUseLocalHostAsDefaultHost feature gate (#3334)
• 20a320c set default address for all parsed receivers (#3333)
• 8eb13f1 Use 0.0.0.0 as otlp receiver default address (#3325)
• e84193d Create a must-gather for the operator (#3150)
• 98433bd Bump go.opentelemetry.io/collector/featuregate from 1.16.0 to 1.17.0 (#3327)
• 0627bf8 Bump kyverno/action-install-chainsaw from 0.2.10 to 0.2.11 (#3326)
• 20ac399 Bump github.com/prometheus/common from 0.59.1 to 0.60.0 (#3329)
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
github.com/open-telemetry/opentelemetry-operator	[>= 1.51.a, < 1.52]

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.