Skip to content

chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 - autoclosed#944

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
Closed

chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 - autoclosed#944
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 5, 2025

This PR contains the following updates:

Package Update Change
ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator minor v0.123.0 -> v0.127.0

Release Notes

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

v0.127.0

Compare Source

0.127.0

💡 Enhancements 💡
  • collector: Move validation to be part of the CRD for sidecar mode (#​3319)

  • target allocator: Promote the operator.collector.targetallocatorcr feature flag to Beta (#​2422)

    As a result of this change, when the target allocator section is enabled in the Collector CR,
    this now creates a TargetAllocator CR instead of generating the manifests directly. Behavior should otherwise be
    unchanged. You can go back to the previous behaviour by passing the
    --feature-gates=-operator.collector.targetallocatorcr command-line option to the operator.

  • collector: Set the default spec.replicas to 1 in the OpenTelemetryCollector CRD. (#​4042)

    This default no longer relies on the admission webhook.

🧰 Bug fixes 🧰
Components

v0.127.0

Compare Source

💡 Enhancements 💡
  • collector: Move validation to be part of the CRD for sidecar mode (#​3319)

  • target allocator: Promote the operator.collector.targetallocatorcr feature flag to Beta (#​2422)

    As a result of this change, when the target allocator section is enabled in the Collector CR,
    this now creates a TargetAllocator CR instead of generating the manifests directly. Behavior should otherwise be
    unchanged. You can go back to the previous behaviour by passing the
    --feature-gates=-operator.collector.targetallocatorcr command-line option to the operator.

  • collector: Set the default spec.replicas to 1 in the OpenTelemetryCollector CRD. (#​4042)

    This default no longer relies on the admission webhook.

🧰 Bug fixes 🧰
Components

v0.126.0

Compare Source

0.126.0

🛑 Breaking changes 🛑
  • target-allocator: Switch to Prometheus 3.0 defaults for ScraperProtocols, requires prometheusreceiver >0.120.0 (#​3872)
💡 Enhancements 💡
  • target-allocator: Allow to configure ScraperProtocols in prometheus common config (#​4000)
  • target allocator: set default target allocator grace period to 30 seconds (#​3989)
    The config option collectorNotReadyGracePeriod have been set to 30s by default. The target allocator now waits for 30 seconds before reallocating targets from a collector which isn't Ready.
    Setting this value to 0 will restore previous behaviour.
🧰 Bug fixes 🧰
  • otel-allocator: Remove overwrite of global config ScraperProtocols (#​3996)
  • target allocator: Fix user-defined volumes in the TargetAllocator CR (#​3992)
  • collector: add terminationGracePeriodSeconds to DaemonSet and StatefulSet specs (#​4003)
Components

v0.126.0

Compare Source

🛑 Breaking changes 🛑
  • target-allocator: Switch to Prometheus 3.0 defaults for ScraperProtocols, requires prometheusreceiver >0.120.0 (#​3872)
💡 Enhancements 💡
  • target-allocator: Allow to configure ScraperProtocols in prometheus common config (#​4000)
  • target allocator: set default target allocator grace period to 30 seconds (#​3989)
    The config option collectorNotReadyGracePeriod have been set to 30s by default. The target allocator now waits for 30 seconds before reallocating targets from a collector which isn't Ready.
    Setting this value to 0 will restore previous behaviour.
🧰 Bug fixes 🧰
  • otel-allocator: Remove overwrite of global config ScraperProtocols (#​3996)
  • target allocator: Fix user-defined volumes in the TargetAllocator CR (#​3992)
  • collector: add terminationGracePeriodSeconds to DaemonSet and StatefulSet specs (#​4003)
Components

v0.125.0

Compare Source

0.125.0

💡 Enhancements 💡
  • webhook: Allow to run the operator without the OpenTelemetry CRDs present (#​3568)
    Skip registering the webhook and keep the operator working in case the OpenTelemetryCollector CRDs are not deployed.
🧰 Bug fixes 🧰
  • collector: Fixes container port duplication for user-provided and operator inferred ports (#​3950)
    This patch improves container port collisions when the user defines additional ports in the CR.

    When ports are specified in the CR:

    • If a port number from the CR matches a port inferred from the config, the inferred port is removed
    • If a port name from the CR matches an inferred port name, the inferred port is renamed to "port-{number}"
  • collector: Prevent the operator from overriding the env vars defined by the user in the OpenTelemetryCollector spec. (#​3963)
    This change ensures that the operator does not override the environment variables defined by the user in the OpenTelemetryCollector spec.
    It combines user-defined environment variables with automatically inferred ones, giving precedence to user-defined ones.

  • opamp: Fix config loading priority (#​3928)

  • target allocator: Fix config loading priority (#​3928)

  • collector: Set the statusReplicas field for the DaemonSet (#​3930)

  • collector: Fix OpenShift internal collector metrics dashboards to use _total suffix (#​3994)
    The following settings (or missing metrics configuration since 0.119.0) exposes metrics with _total suffix:

       service:
         telemetry:
           metrics:
             readers:
              - pull:
                exporter:
                  prometheus:
                    host: '0.0.0.0'
                    port: 8888

    The following settings exposes metrics without _total suffix:

       service:
         telemetry:
             address: 0.0.0.0:8888
  • targetallocator: Do not override the collector namespace from the config file if the environment variable is not set. (#​3976)

Components

v0.125.0

Compare Source

💡 Enhancements 💡
  • webhook: Allow to run the operator without the OpenTelemetry CRDs present (#​3568)
    Skip registering the webhook and keep the operator working in case the OpenTelemetryCollector CRDs are not deployed.
🧰 Bug fixes 🧰
  • collector: Fixes container port duplication for user-provided and operator inferred ports (#​3950)
    This patch improves container port collisions when the user defines additional ports in the CR.

    When ports are specified in the CR:

    • If a port number from the CR matches a port inferred from the config, the inferred port is removed
    • If a port name from the CR matches an inferred port name, the inferred port is renamed to "port-{number}"
  • collector: Prevent the operator from overriding the env vars defined by the user in the OpenTelemetryCollector spec. (#​3963)
    This change ensures that the operator does not override the environment variables defined by the user in the OpenTelemetryCollector spec.
    It combines user-defined environment variables with automatically inferred ones, giving precedence to user-defined ones.

  • opamp: Fix config loading priority (#​3928)

  • target allocator: Fix config loading priority (#​3928)

  • collector: Set the statusReplicas field for the DaemonSet (#​3930)

  • collector: Fix OpenShift internal collector metrics dashboards to use _total suffix (#​3994)
    The following settings (or missing metrics configuration since 0.119.0) exposes metrics with _total suffix:

       service:
         telemetry:
           metrics:
             readers:
              - pull:
                exporter:
                  prometheus:
                    host: '0.0.0.0'
                    port: 8888

    The following settings exposes metrics without _total suffix:

       service:
         telemetry:
             address: 0.0.0.0:8888
  • targetallocator: Do not override the collector namespace from the config file if the environment variable is not set. (#​3976)

Components

v0.124.0

Compare Source

0.124.0

💡 Enhancements 💡
  • collector: Re-try failed upgrades (#​3515)
    The upgrade process runs now in the reconcile loop.
    In case of an error, the operator re-tries the upgrade with exponential backoff.
Components

v0.124.0

Compare Source

💡 Enhancements 💡
  • collector: Re-try failed upgrades (#​3515)
    The upgrade process runs now in the reconcile loop.
    In case of an error, the operator re-tries the upgrade with exponential backoff.
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 becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner June 5, 2025 14:30
@github-actions
Copy link
Contributor

github-actions bot commented Jun 5, 2025

⚠️ Action Required: Update Your README.md! 📜🚀

📌 The README.md for one or more plugins is outdated due to changes in values.yaml. Please update it by running the following command(s):

make generate-readme PLUGIN=logs

✅ Once you've done that, commit the updated README and push it to this branch.

@renovate renovate bot changed the title chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 - autoclosed Jun 11, 2025
@renovate renovate bot closed this Jun 11, 2025
@renovate renovate bot deleted the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch June 11, 2025 21:58
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 - autoclosed chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 Jun 12, 2025
@renovate renovate bot reopened this Jun 12, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch from 45c8d66 to 4333d17 Compare June 12, 2025 12:38
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.127.0 - autoclosed Jun 16, 2025
@renovate renovate bot closed this Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants