Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 23, 2024

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

Release notes

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

Release v0.115.0

0.115.0

💡 Enhancements 💡

  • collector: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)
  • collector: support for creating a service for extensions when ports are specified. (#3460)

🧰 Bug fixes 🧰

  • github action: Add new line character at the end of PrometheusRule file. (#3503)

  • auto-instrumentation: Reverts PR 3379 which inadvertently broke users setting JAVA_TOOL_OPTIONS (#3463) Reverts a previous PR which was causing JAVA_TOOL_OPTIONS to not be overriden when set by users. This was resulting in application crashloopbackoffs for users relying on java autoinstrumentation.

  • auto-instrumentation: Remove the mapping of app.kubernetes.io/instance to service.instance.id (#3495) Technically, this is a breaking change, but we regard it as a bug fix because the previous behavior was incorrect.

    if you did have multiple container instrumentation and use app.kubernetes.io/instance to set the service.instance.id, you will now see multiple instances in the UI - which is the correct behavior.

    You can still use the attribute resource.opentelemetry.io/service.instance.id to set the service.instance.id, which will be shared across all containers in the pod - but this is not recommended for multiple container instrumentation instances.

    Refer to the semantic conventions for more information.

Components

Release v0.114.1

0.114.1

🧰 Bug fixes 🧰

  • auto-instrumentation: Reverts PR 3379 which inadvertently broke users setting JAVA_TOOL_OPTIONS (#3463) Reverts a previous PR which was causing JAVA_TOOL_OPTIONS to not be overriden when set by users. This was resulting in application crashloopbackoffs for users relying on java autoinstrumentation.

... (truncated)

Changelog

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

0.115.0

💡 Enhancements 💡

  • collector: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)
  • collector: support for creating a service for extensions when ports are specified. (#3460)

🧰 Bug fixes 🧰

  • github action: Add new line character at the end of PrometheusRule file. (#3503)

  • auto-instrumentation: Reverts PR 3379 which inadvertently broke users setting JAVA_TOOL_OPTIONS (#3463) Reverts a previous PR which was causing JAVA_TOOL_OPTIONS to not be overriden when set by users. This was resulting in application crashloopbackoffs for users relying on java autoinstrumentation.

  • auto-instrumentation: Remove the mapping of app.kubernetes.io/instance to service.instance.id (#3495) Technically, this is a breaking change, but we regard it as a bug fix because the previous behavior was incorrect.

    if you did have multiple container instrumentation and use app.kubernetes.io/instance to set the service.instance.id, you will now see multiple instances in the UI - which is the correct behavior.

    You can still use the attribute resource.opentelemetry.io/service.instance.id to set the service.instance.id, which will be shared across all containers in the pod - but this is not recommended for multiple container instrumentation instances.

    Refer to the semantic conventions for more information.

Components

0.114.1

🧰 Bug fixes 🧰

  • auto-instrumentation: Reverts PR 3379 which inadvertently broke users setting JAVA_TOOL_OPTIONS (#3463) Reverts a previous PR which was causing JAVA_TOOL_OPTIONS to not be overriden when set by users. This was resulting in application crashloopbackoffs for users relying on java autoinstrumentation.
  • github action: Add new line character at the end of PrometheusRule file. (#3503)

... (truncated)

Commits

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
github.com/open-telemetry/opentelemetry-operator [>= 1.51.a, < 1.52]

Dependabot compatibility score

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 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)

Bumps [github.com/open-telemetry/opentelemetry-operator](https://github.com/open-telemetry/opentelemetry-operator) from 0.103.0 to 0.115.0.
- [Release notes](https://github.com/open-telemetry/opentelemetry-operator/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-operator/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-operator@v0.103.0...v0.115.0)

---
updated-dependencies:
- dependency-name: github.com/open-telemetry/opentelemetry-operator
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
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