Skip to content

Conversation

@jarvis-plus-bot
Copy link
Contributor

@jarvis-plus-bot jarvis-plus-bot bot commented Jan 28, 2026

This PR contains the following updates:

Package Update Change OpenSSF
ghcr.io/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator minor 0.102.00.105.0 OpenSSF Scorecard

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

open-telemetry/opentelemetry-operator (ghcr.io/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator)

v0.105.0

Compare Source

💡 Enhancements 💡
  • collector: Create automatically an OpenShift dashboard to visualize OpenTelemetry Collector metrics (#​2995)
    To enable this feature, you need to specify the --openshift-create-dashboard argument to the operator
  • bundle: Create an specific bundle for OpenShift environments. (#​3054)
  • collector: Enabling ipFamilies and ipFamilyPolicy to be configured via OpenTelemetryCollector (#​2958)
  • auto-instrumentation: Add Prometheus exporter to Python auto-instrumentation (#​3122)
  • collector: Configmap, rbac, service, serviceaccount apply annotations-filter. (#​3151)
🧰 Bug fixes 🧰
  • collector: Remove workaround for 0.104.0 that enabled feature-gate confmap.unifyEnvVarExpansion when Prometheus receiver was enabled. (#​3142)
  • opamp: Fixes a bug where the collector was not being marshalled correctly by using a reference instead of a value. (#​3171)
  • auto-instrumentation: Fixes a bug statefulSet wrong service.instance.id (#​3157)
Components

v0.104.0

Compare Source

🛑 Breaking changes 🛑
  • opamp: Adds support for v1beta1 OpenTelemetry Collector API in the OpAMP Bridge (#​2985)
    This change adds support for the OpAMP Bridge to manage and apply OpenTelemetry Collectors using the v1beta1 API in
    the OpAMP Bridge. This change removes support for applying OpenTelemetry Collectors using the v1alpha1 API version.
    The v1beta1 API is the latest version of the OpenTelemetry Collector API and is the recommended version for new
    deployments.
💡 Enhancements 💡
  • collector: Since collector version 0.104.0 the collector listens on localhost instead of 0.0.0.0 by default (collector#8510). To avoid breaking changes the component.UseLocalHostAsDefaultHost feature-gate is disabled by the Operator. (#​3119)
  • collector: Changes the default parser to silently fail. (#​3133)
  • collector, target allocator: If the target allocator is enabled, the collector featuregate `confmap.unifyEnvVarExpansion' is disabled. (#​3119)
  • operator: Release leader election lease on exit (#​3058)
  • collector, target allocator, opamp: Enabling PodDnsConfig for OpenTelemetry Collector, TargetAllocator and OpAMPBridge. (#​2658)
  • collector: Make the spec.mode field of the OpenTelemetryCollector Custom Resource (CR) immutable (#​3055)
  • collector: Improves the performance of port and configuration parsing in the operator (#​2603)
🧰 Bug fixes 🧰
  • collector: Fixes a bug where an exporter would cause a port collision (#​3124)

  • collector: Fix deletion issue of otelcol CR by making spec.config.service.pipelines.processors optional (#​3075)
    This change makes spec.config.service.pipelines.processors in OpenTelemetryCollector CRD optional, aligning with OTel Collector best practices. It resolves deletion issues by providing flexibility in CRD configuration, addressing conflicts between strict validation and practical uses.
    Note: Updating the opentelemetrycollectors.opentelemetry.io CRD resource is required.

  • collector: Allow annotations on service account to prevent infinite reconciliation on OpenShift and creating infinite pull secrets. (#​3106)
    On OpenShift 4.16 the platform automatically adds an annotation openshift.io/internal-registry-pull-secret-ref: <simplest-collector-dockercfg-jwq66>
    to the service account which contains secret name with image pull secret.

Components

v0.103.0

Compare Source

💡 Enhancements 💡
  • collector, target allocator, opamp: Require Go 1.22 for building the operator (#​2757)
🧰 Bug fixes 🧰
  • auto-instrumentation: Fix webserver instrumentation log file name (#​2978)

    Since webserver instrumentation 1.0.4, the configuration log file has been renamed from appdynamics_sdk_log4cxx.xml.template to opentelemetry_sdk_log4cxx.xml.template. The operator upgraded the webserver instrumentation version but haven't change the configuration file name.

  • target-allocator: Fixes a bug that didn't automatically create a PDB for a TA with per-node strategy (#​2900)

Components

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@jarvis-plus-bot
Copy link
Contributor Author

no HelmRelease objects found in cluster

@jarvis-plus-bot jarvis-plus-bot bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-helm-charts-opentelemetry-operator-0.x branch from e0f814e to a7c2645 Compare January 28, 2026 17:12
@jarvis-plus-bot jarvis-plus-bot bot changed the title feat(container): update image ghcr.io/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator ( 0.102.0 → 0.103.0 ) feat(container): update image ghcr.io/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator ( 0.102.0 → 0.105.0 ) Jan 28, 2026
@jarvis-plus-bot jarvis-plus-bot bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-helm-charts-opentelemetry-operator-0.x branch 13 times, most recently from 9924e2b to a96a87f Compare February 3, 2026 16:18
…lm-charts/opentelemetry-operator ( 0.102.0 → 0.105.0 )
@jarvis-plus-bot jarvis-plus-bot bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-helm-charts-opentelemetry-operator-0.x branch from a96a87f to 94374e7 Compare February 3, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants