chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.116.0 #458
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
branch
from
0f8c0b5 to
8f648f4
Compare
renovate
bot
force-pushed
the
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
branch
from
8f648f4 to
0272794
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
branch
2 times, most recently
from
6e09a96 to
5ade6ab
Compare
renovate
bot
force-pushed
the
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
branch
from
5ade6ab to
c8221c0
Compare
renovate
bot
changed the title
…ntelemetry-operator docker tag to v0.116.0
renovate
bot
force-pushed
the
renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x
branch
from
c8221c0 to
d613032
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.114.1->v0.116.0Warning
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-operator/opentelemetry-operator)
v0.116.0Compare Source
0.116.0
💡 Enhancements 💡
target allocator: Process discovered targets asyncchronously (#1842)This change enables the target allocator to process discovered targets asynchronously.
This is a significant performance improvement for the target allocator, as it allows it to process targets in parallel, rather than sequentially.
This change also introduces new metrics to track the performance of the target allocator.
🧰 Bug fixes 🧰
operator: Fix the admission webhook to when metrics service address host uses env var expansion (#3513)This should allow the metrics service address to have the host portion expanded from an environment variable,
like
$(env:POD_IP)instead of using0.0.0.0, which is the recommended by the Collector.auto-instrumentation: Apache instrumentation sidecar fails to start if target container define lifecycle (#3547)collector: Fix deletion of optional resources for OpenTelemetryCollector CRs (#3454)Components
v0.116.0Compare Source
💡 Enhancements 💡
target allocator: Process discovered targets asyncchronously (#1842)This change enables the target allocator to process discovered targets asynchronously.
This is a significant performance improvement for the target allocator, as it allows it to process targets in parallel, rather than sequentially.
This change also introduces new metrics to track the performance of the target allocator.
🧰 Bug fixes 🧰
operator: Fix the admission webhook to when metrics service address host uses env var expansion (#3513)This should allow the metrics service address to have the host portion expanded from an environment variable,
like
$(env:POD_IP)instead of using0.0.0.0, which is the recommended by the Collector.auto-instrumentation: Apache instrumentation sidecar fails to start if target container define lifecycle (#3547)collector: Fix deletion of optional resources for OpenTelemetryCollector CRs (#3454)Components
v0.115.0Compare Source
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 ofapp.kubernetes.io/instancetoservice.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/instanceto set theservice.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.idto set theservice.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
v0.115.0Compare Source
💡 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 ofapp.kubernetes.io/instancetoservice.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/instanceto set theservice.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.idto set theservice.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
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.
This PR was generated by Mend Renovate. View the repository job log.