build(deps): bump github.com/open-telemetry/opentelemetry-operator/apis from 0.157.0 to 0.158.0

[dependabot]

Bumps github.com/open-telemetry/opentelemetry-operator/apis from 0.157.0 to 0.158.0.

Release notes

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

Release v0.158.0

0.158.0

💡 Enhancements 💡

• operator, collector, target allocator: Enable operator, collector, target allocator network policies by default. (#5394) Feature gate operator.networkpolicy and operand.networkpolicy are promoted to beta, and enabled by default. These feature gates create network policies for the operator and operand components.

• auto-instrumentation: Apache and nginx instrumentations forward Spec env vars to attach init containers so kubelet can expand $(VAR) references in exporter endpoints. (#5333)

• collector: promote the operator.collector.usedefaulttelemetryshape feature gate to stable, so the operator-injected Prometheus telemetry reader always uses collector defaults for without_type_suffix, without_units, and without_scope_info (#5075) The gate is now stable and can no longer be disabled. Users wanting the pre-v0.154.0 metric name shape should explicitly set without_type_suffix, without_units, and without_scope_info to false in their collector configuration. The gate will be removed in a future release.

• collector: moves operator.golang.flags to stable setting GOMEMLIMIT and GOMAXPROCS automatically (#5455)

🧰 Bug fixes 🧰

• collector: Fix the automatic-upgrade routine binding two Prometheus readers to the same port when a collector already uses service.telemetry.metrics.readers. (#5416) When an OpenTelemetryCollector already configured service.telemetry.metrics.readers (added by earlier defaulting), the automatic version-upgrade routine still backfilled the older, deprecated address field for it. The 0.122.0 upgrade step then migrated address into a new reader, leaving two readers bound to the same host:port. The collector then failed to start with "address already in use". The 0.111.0 step now skips backfilling address when readers is already configured, and the 0.122.0 step now skips adding a reader for address if an equivalent one already exists.
• collector: Add PersistentVolume and PersistentVolumeClaim RBAC rules for k8s_cluster receiver automatic RBAC generation. (#5421)
• auto-instrumentation: Default OTEL_METRICS_EXPORTER to otlp for Node.js auto-instrumentation so metrics are exported without extra configuration. (#3768) The Node.js SDK only initializes its metrics pipeline when a metric reader is configured, and the webhook was not setting one. As a result, metrics silently stopped being exported for anyone relying on the previous default behavior. The webhook now sets OTEL_METRICS_EXPORTER=otlp by default, matching the existing behavior for Python auto-instrumentation, unless the user already set it.

Components

• OpenTelemetry Collector - v0.158.0
• OpenTelemetry Contrib - v0.158.0
• Java auto-instrumentation - v2.30.0
• .NET auto-instrumentation - v1.16.0
• Node.JS - v0.78.0
• Python - v0.64b0
• Go - v0.24.0
• ApacheHTTPD - 1.0.4
• Nginx - 1.0.4

Changelog

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

0.158.0

💡 Enhancements 💡

• operator, collector, target allocator: Enable operator, collector, target allocator network policies by default. (#5394) Feature gate operator.networkpolicy and operand.networkpolicy are promoted to beta, and enabled by default. These feature gates create network policies for the operator and operand components.

• auto-instrumentation: Apache and nginx instrumentations forward Spec env vars to attach init containers so kubelet can expand $(VAR) references in exporter endpoints. (#5333)

• collector: promote the operator.collector.usedefaulttelemetryshape feature gate to stable, so the operator-injected Prometheus telemetry reader always uses collector defaults for without_type_suffix, without_units, and without_scope_info (#5075) The gate is now stable and can no longer be disabled. Users wanting the pre-v0.154.0 metric name shape should explicitly set without_type_suffix, without_units, and without_scope_info to false in their collector configuration. The gate will be removed in a future release.

• collector: moves operator.golang.flags to stable setting GOMEMLIMIT and GOMAXPROCS automatically (#5455)

🧰 Bug fixes 🧰

• collector: Fix the automatic-upgrade routine binding two Prometheus readers to the same port when a collector already uses service.telemetry.metrics.readers. (#5416) When an OpenTelemetryCollector already configured service.telemetry.metrics.readers (added by earlier defaulting), the automatic version-upgrade routine still backfilled the older, deprecated address field for it. The 0.122.0 upgrade step then migrated address into a new reader, leaving two readers bound to the same host:port. The collector then failed to start with "address already in use". The 0.111.0 step now skips backfilling address when readers is already configured, and the 0.122.0 step now skips adding a reader for address if an equivalent one already exists.
• collector: Add PersistentVolume and PersistentVolumeClaim RBAC rules for k8s_cluster receiver automatic RBAC generation. (#5421)
• auto-instrumentation: Default OTEL_METRICS_EXPORTER to otlp for Node.js auto-instrumentation so metrics are exported without extra configuration. (#3768) The Node.js SDK only initializes its metrics pipeline when a metric reader is configured, and the webhook was not setting one. As a result, metrics silently stopped being exported for anyone relying on the previous default behavior. The webhook now sets OTEL_METRICS_EXPORTER=otlp by default, matching the existing behavior for Python auto-instrumentation, unless the user already set it.

Components

• OpenTelemetry Collector - v0.158.0
• OpenTelemetry Contrib - v0.158.0
• Java auto-instrumentation - v2.30.0
• .NET auto-instrumentation - v1.16.0
• Node.JS - v0.78.0
• Python - v0.64b0
• Go - v0.24.0
• ApacheHTTPD - 1.0.4
• Nginx - 1.0.4

Commits

• 7fb5138 Prepare release 0.158.0 (#5463)
• 5bc2242 Promote the operator.collector.usedefaulttelemetryshape feature gate to stabl...
• 320da5c Make network policy feature gate enabled (beta) (#5461)
• 72ee786 Update module github.com/stretchr/testify to v1.12.0 (#5474)
• ccfd507 Update github.com/openshift/controller-runtime-common digest to e1187ec (#5468)
• bf41863 Update test base images (#5472)
• f12d529 Update github.com/openshift/api digest to d4bb0b4 (#5467)
• 9853524 Update github.com/openshift/library-go digest to a0584a6 (#5469)
• 517d80c Update production base images (#5470)
• 76ff658 Update github/codeql-action action to v4.37.7 (#5471)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign peteryurkovich 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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a rhobs 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.

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.