🌱 bump github.com/open-telemetry/opentelemetry-operator/apis from 0.153.0 to 0.154.0

[dependabot]

Bumps github.com/open-telemetry/opentelemetry-operator/apis from 0.153.0 to 0.154.0.

Release notes

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

Release v0.154.0

0.154.0

🛑 Breaking changes 🛑

• collector: Promote the operator.collector.usedefaulttelemetryshape feature gate to beta. The operator-injected Prometheus telemetry reader now uses collector defaults by default — metric names from operator-managed collectors no longer carry type suffixes, units, or scope_info. (#5075) Users wanting the pre-v0.154.0 metric name shape can disable the gate via --feature-gates=-operator.collector.usedefaulttelemetryshape, or pin without_type_suffix/without_units/without_scope_info to false explicitly under spec.config.service.telemetry. The gate will be promoted to stable and removed in a future release.

💡 Enhancements 💡

• collector: Add status.observedGeneration and status.conditions support for OpenTelemetryCollector resources. (#4312)

• operator: Add pod-webhook subcommand for running a standalone pod mutation webhook (#5010) The operator binary now supports a pod-webhook subcommand that runs only the pod mutation webhook (auto-instrumentation and sidecar injection) without the controllers. This enables deploying the webhook separately.

• opampbridge: Add TLS configuration support to the OpAMP Bridge, including options to disable TLS or skip certificate verification. (#4921)

• opamp: Allow standalone OpAMP bridge agents to configure per-agent non-identifying attributes. (#5245)

• opamp-bridge: Make standalone OpAMP Bridge manifests and runtime permissions friendlier for OpenShift and namespaced RBAC. (#5277)

• operator: Add standalone pod webhook deployment for High Availability on OpenShift (#5010) On OpenShift with OLM, the pod mutation webhook (auto-instrumentation and sidecar injection) is now deployed as a standalone Deployment with 2 replicas by default, enabling HA.

  OpenShift with OLM:

  • The standalone webhook deployment is managed by OLM via the CSV
  • Default: 2 replicas for HA
  • Pod anti-affinity spreads replicas across different nodes
  • PodDisruptionBudget with maxUnavailable: 1 ensures availability during node maintenance
  • Only scaling down is supported via OPENSHIFT_WEBHOOK_REPLICAS env var in the Subscription (0 or 1)
  • TLS certificates are automatically provisioned by OLM
  • Automatic cleanup when operator is uninstalled (OLM garbage collection)

  Kubernetes (community bundle):

  • No change - pod webhook continues to run as part of the operator deployment

• opamp-bridge: OpAMP Bridge standalone mode (#4913) Standalone mode for OpAMP Bridge allows users to manage collector configuration from a remote OpAMP server without the need to deploy full Otel Operator.

• operator: Move all webhooks to the dedicated webhook deployment. (#5010) This change moves remaining webhooks (defaulting, validating for: Collector, TargetAllocator, Instrumentation, OpAMPBridge) to the dedicated webhook deployment. Previously, only the pod mutation webhook was served by the webhook deployment, while the other webhooks were served by the controller-manager. The dedicated webhook deployment is opt-in and enabled by default only on OpenShift with OLM.

🧰 Bug fixes 🧰

• target allocator: Fix silent target loss when group labels are present in static_configs by sorting labels globally in processTargetGroups. (#4967) ScratchBuilder.Labels() serializes labels in insertion order. When group labels sort

... (truncated)

Changelog

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

0.154.0

🛑 Breaking changes 🛑

• collector: Promote the operator.collector.usedefaulttelemetryshape feature gate to beta. The operator-injected Prometheus telemetry reader now uses collector defaults by default — metric names from operator-managed collectors no longer carry type suffixes, units, or scope_info. (#5075) Users wanting the pre-v0.154.0 metric name shape can disable the gate via --feature-gates=-operator.collector.usedefaulttelemetryshape, or pin without_type_suffix/without_units/without_scope_info to false explicitly under spec.config.service.telemetry. The gate will be promoted to stable and removed in a future release.

💡 Enhancements 💡

• collector: Add status.observedGeneration and status.conditions support for OpenTelemetryCollector resources. (#4312)

• operator: Add pod-webhook subcommand for running a standalone pod mutation webhook (#5010) The operator binary now supports a pod-webhook subcommand that runs only the pod mutation webhook (auto-instrumentation and sidecar injection) without the controllers. This enables deploying the webhook separately.

• opampbridge: Add TLS configuration support to the OpAMP Bridge, including options to disable TLS or skip certificate verification. (#4921)

• opamp: Allow standalone OpAMP bridge agents to configure per-agent non-identifying attributes. (#5245)

• opamp-bridge: Make standalone OpAMP Bridge manifests and runtime permissions friendlier for OpenShift and namespaced RBAC. (#5277)

• operator: Add standalone pod webhook deployment for High Availability on OpenShift (#5010) On OpenShift with OLM, the pod mutation webhook (auto-instrumentation and sidecar injection) is now deployed as a standalone Deployment with 2 replicas by default, enabling HA.

  OpenShift with OLM:

  • The standalone webhook deployment is managed by OLM via the CSV
  • Default: 2 replicas for HA
  • Pod anti-affinity spreads replicas across different nodes
  • PodDisruptionBudget with maxUnavailable: 1 ensures availability during node maintenance
  • Only scaling down is supported via OPENSHIFT_WEBHOOK_REPLICAS env var in the Subscription (0 or 1)
  • TLS certificates are automatically provisioned by OLM
  • Automatic cleanup when operator is uninstalled (OLM garbage collection)

  Kubernetes (community bundle):

  • No change - pod webhook continues to run as part of the operator deployment

• opamp-bridge: OpAMP Bridge standalone mode (#4913) Standalone mode for OpAMP Bridge allows users to manage collector configuration from a remote OpAMP server without the need to deploy full Otel Operator.

• operator: Move all webhooks to the dedicated webhook deployment. (#5010) This change moves remaining webhooks (defaulting, validating for: Collector, TargetAllocator, Instrumentation, OpAMPBridge) to the dedicated webhook deployment. Previously, only the pod mutation webhook was served by the webhook deployment, while the other webhooks were served by the controller-manager. The dedicated webhook deployment is opt-in and enabled by default only on OpenShift with OLM.

🧰 Bug fixes 🧰

• target allocator: Fix silent target loss when group labels are present in static_configs by sorting labels globally in processTargetGroups. (#4967) ScratchBuilder.Labels() serializes labels in insertion order. When group labels sort alphabetically after target labels (e.g. vendor > address), Labels.Get() early

... (truncated)

Commits

• 33bb60f prep release 0.154.0 (#5283)
• 7747b2b Adjust the webhook RFC after the implementation (#5282)
• 8b8adc0 Fix OpenShift webhook deployment (#5281)
• d9fc6e9 Add remaining webhooks to the webhook deployment (#5279)
• ec91574 Upload test coverage information to codecov (#5261)
• 68fe023 chore: remove temporary changelog (#5280)
• 2cf57d7 Make instrumentation webhook HA on OpenShift (#5273)
• 6084855 Make OPAMP Bridge more OpenShift friendly (#5278)
• 667f349 Fix operator NetworkPolicy crash on OpenShift due to mixed ipBlock and select...
• 1111a26 Update k8s.io/utils digest to be93311 (#5262)
• 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)

[gardener-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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