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.106.0 in /tests #3822

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 12, 2024

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

Release notes

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

Release v0.106.0

0.106.0

🧰 Bug fixes 🧰

  • collector: Fixes a bug where the operator would default the PDB in the wrong place. (#3198)
  • operator: The OpenShift dashboard shown namespaces where PodMonitors or ServiceMonitors were created even if they were not associated to OpenTelemetry Collectors. (#3196) Now, the dashboard lists only those namespaces where there are OpenTelemetry Collectors.
  • operator: When there were multiple OpenTelemetry Collector, the dashboard doesn't allow to select them individually. (#3189)
  • target allocator: Fix collector to target allocator connection in clusters with proxy. (#3187) On clusters with global proxy the collector might fail to talk to target allocator because the endpoint is set to <ta-service-name>:port and therefore it will go to proxy and request might be forwarded to internet. Clusters with proxy configure NO_PROXY to .svc.cluster.local so the calls to this endpoint will not go through the proxy.

Components

Release v0.105.0

0.105.0

💡 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 🧰

... (truncated)

Changelog

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

0.106.0

🧰 Bug fixes 🧰

  • collector: Fixes a bug where the operator would default the PDB in the wrong place. (#3198)
  • operator: The OpenShift dashboard shown namespaces where PodMonitors or ServiceMonitors were created even if they were not associated to OpenTelemetry Collectors. (#3196) Now, the dashboard lists only those namespaces where there are OpenTelemetry Collectors.
  • operator: When there were multiple OpenTelemetry Collector, the dashboard doesn't allow to select them individually. (#3189)
  • target allocator: Fix collector to target allocator connection in clusters with proxy. (#3187) On clusters with global proxy the collector might fail to talk to target allocator because the endpoint is set to <ta-service-name>:port and therefore it will go to proxy and request might be forwarded to internet. Clusters with proxy configure NO_PROXY to .svc.cluster.local so the calls to this endpoint will not go through the proxy.

Components

0.105.0

💡 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

... (truncated)

Commits
  • c839f73 Prepare release 0.106.0 (#3202)
  • 0551975 Fix pdb defaulting logic (#3200)
  • 92652a5 Fix listing only namespaces containing OpenTelemetry Collector instances. Fix...
  • eab0b6a chore: update python auto-instrumentation dependencies 1.26.0/0.47b0 (#3175)
  • e520f5b Bump kyverno/action-install-chainsaw from 0.2.7 to 0.2.8 (#3195)
  • b20fbd5 Fix TA in clusters with global proxy (#3187)
  • 745ba08 Fix monitoring test case (#3185)
  • f66f3f6 Fix dropdown menu to select individual OpenTelemetry Collector instances. Clo...
  • 93cdc28 replace logging with debug in all tests (#3192)
  • 2fbc1fd Release 0.105.0 (#3164)
  • Additional commits viewable in compare view

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.106.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.106.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] <support@github.com>
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 19, 2024

Superseded by #3827.

@dependabot dependabot bot closed this Aug 19, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/tests/github.com/open-telemetry/opentelemetry-operator-0.106.0 branch August 19, 2024 01:09
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