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

renovate · 2024-10-22T07:54:08Z

This PR contains the following updates:

Package	Update	Change
ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator	minor	`v0.110.0` -> `v0.113.0`

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-operator/opentelemetry-operator)

`v0.113.0`

Compare Source

0.113.0

💡 Enhancements 💡

operator: Programmatically create the ServiceMonitor for the operator metrics endpoint, ensuring correct namespace handling and dynamic configuration. (#3370)
Previously, the ServiceMonitor was created statically from a manifest file, causing failures when the
operator was deployed in a non-default namespace. This enhancement ensures automatic adjustment of the
serverName and seamless metrics scraping.
collector: Create RBAC rules for the k8s_events receiver automatically. (#3420)
collector: Inject environment K8S_NODE_NAME environment variable for the Kubelet Stats Receiver. (#2779)
auto-instrumentation: add config for installing musl based auto-instrumentation for Python (#2264)
auto-instrumentation: Support http/json and http/protobuf via OTEL_EXPORTER_OTLP_PROTOCOL environment variable in addition to default grpc for exporting traces (#3412)
target allocator: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)

🧰 Bug fixes 🧰

collector: Fix mutation of deployments, statefulsets, and daemonsets allowing to remove fields on update (#2947)

Components

`v0.113.0`

Compare Source

💡 Enhancements 💡

operator: Programmatically create the ServiceMonitor for the operator metrics endpoint, ensuring correct namespace handling and dynamic configuration. (#3370)
Previously, the ServiceMonitor was created statically from a manifest file, causing failures when the
operator was deployed in a non-default namespace. This enhancement ensures automatic adjustment of the
serverName and seamless metrics scraping.
collector: Create RBAC rules for the k8s_events receiver automatically. (#3420)
collector: Inject environment K8S_NODE_NAME environment variable for the Kubelet Stats Receiver. (#2779)
auto-instrumentation: add config for installing musl based auto-instrumentation for Python (#2264)
auto-instrumentation: Support http/json and http/protobuf via OTEL_EXPORTER_OTLP_PROTOCOL environment variable in addition to default grpc for exporting traces (#3412)
target allocator: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)

🧰 Bug fixes 🧰

collector: Fix mutation of deployments, statefulsets, and daemonsets allowing to remove fields on update (#2947)

Components

`v0.112.0`

Compare Source

0.112.0

💡 Enhancements 💡

auto-instrumentation: Support configuring Java auto-instrumentation when runtime configuration is provided from configmap or secret. (#1814)
This change allows users to configure JAVA_TOOL_OPTIONS in config map or secret when the name of the variable is defined in the pod spec.
The operator in this case set another JAVA_TOOL_OPTIONS that references the original value
e.g. JAVA_TOOL_OPTIONS=$(JAVA_TOOL_OPTIONS) -javaagent:/otel-auto-instrumentation-java/javaagent.jar.
auto-instrumentation: Adds VolumeClaimTemplate field to Instrumentation spec to enable user-definable ephemeral volumes for auto-instrumentation. (#3267)
collector: Add support for persistentVolumeClaimRetentionPolicy field (#3305)
auto-instrumentation: build musl based auto-instrumentation in Python docker image (#2264)
auto-instrumentation: An empty line should come before the addition of Include ...opentemetry_agent.conf, as a protection measure against cases of httpd.conf w/o a blank last line (#3401)
collector: Add automatic RBAC creation for the kubeletstats receiver. (#3155)
auto-instrumentation: Add Nodejs auto-instrumentation image builds for linux/s390x,linux/ppc64le. (#3322)

🧰 Bug fixes 🧰

target allocator: Permission check fixed for the serviceaccount of the target allocator (#3380)
target allocator: Change docker image to run as non-root (#3378)

Components

`v0.112.0`

Compare Source

💡 Enhancements 💡

auto-instrumentation: Support configuring Java auto-instrumentation when runtime configuration is provided from configmap or secret. (#1814)
This change allows users to configure JAVA_TOOL_OPTIONS in config map or secret when the name of the variable is defined in the pod spec.
The operator in this case set another JAVA_TOOL_OPTIONS that references the original value
e.g. JAVA_TOOL_OPTIONS=$(JAVA_TOOL_OPTIONS) -javaagent:/otel-auto-instrumentation-java/javaagent.jar.
auto-instrumentation: Adds VolumeClaimTemplate field to Instrumentation spec to enable user-definable ephemeral volumes for auto-instrumentation. (#3267)
collector: Add support for persistentVolumeClaimRetentionPolicy field (#3305)
auto-instrumentation: build musl based auto-instrumentation in Python docker image (#2264)
auto-instrumentation: An empty line should come before the addition of Include ...opentemetry_agent.conf, as a protection measure against cases of httpd.conf w/o a blank last line (#3401)
collector: Add automatic RBAC creation for the kubeletstats receiver. (#3155)
auto-instrumentation: Add Nodejs auto-instrumentation image builds for linux/s390x,linux/ppc64le. (#3322)

🧰 Bug fixes 🧰

target allocator: Permission check fixed for the serviceaccount of the target allocator (#3380)
target allocator: Change docker image to run as non-root (#3378)

Components

`v0.111.0`

Compare Source

0.111.0

💡 Enhancements 💡

auto-instrumentation: set OTEL_LOGS_EXPORTER env var to otlp in python instrumentation (#3330)
collector: Expose the Collector telemetry endpoint by default. (#3361)

The collector v0.111.0 changes the default binding of the telemetry metrics endpoint from 0.0.0.0 to localhost.
To avoid any disruption we fallback to 0.0.0.0:{PORT} as default address.
Details can be found here: opentelemetry-collector#11251
auto-instrumentation: Add support for specifying exporter TLS certificates in auto-instrumentation. (#3338)

Now Instrumentation CR supports specifying TLS certificates for exporter:
```
spec:
  exporter:
    endpoint: https://otel-collector:4317
    tls:
      secretName: otel-tls-certs
      configMapName: otel-ca-bundle
```

otel-ca-bundle

    ca_file: ca.crt

present in otel-tls-certs

    cert_file: tls.crt

present in otel-tls-certs

    key_file: tls.key


* Propagating secrets across namespaces can be done with https://github.com/EmberStack/kubernetes-reflector or https://github.com/zakkg3/ClusterSecret
* Restarting workloads on certificate renewal can be done with https://github.com/stakater/Reloader or https://github.com/wave-k8s/wave

- `collector`: Add native sidecar injection behind a feature gate which is disabled by default. (#&#8203;2376)

Native sidecars are supported since Kubernetes version `1.28` and are availabe by default since `1.29`.
To use native sidecars on Kubernetes v1.28 make sure the "SidecarContainers" feature gate on kubernetes is enabled.
If native sidecars are available, the operator can be advised to use them by adding
the `--feature-gates=operator.sidecarcontainers.native` to the Operator args.
In the future this may will become availabe as deployment mode on the Collector CR. See [#&#8203;3356](https://redirect.github.com/open-telemetry/opentelemetry-operator/issues/3356)

- `target allocator, collector`: Enable mTLS between the TA and collector for passing secrets in the scrape_config securely (#&#8203;1669)

This change enables mTLS between the collector and the target allocator (requires cert-manager).
This is necessary for passing secrets securely from the TA to the collector for scraping endpoints that have authentication. Use the `operator.targetallocator.mtls` to enable this feature. See the target allocator [documentation](https://redirect.github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator#service--pod-monitor-endpoint-credentials) for more details.

##### 🧰 Bug fixes 🧰

- `collector-webhook`: Fixed validation of `stabilizationWindowSeconds` in autoscaler behaviour (#&#8203;3345)

The validation of `stabilizationWindowSeconds` in the `autoscaler.behaviour.scale[Up|Down]` incorrectly rejected 0 as an invalid value.
This has been fixed to ensure that the value is validated correctly (should be >=0 and <=3600) and the error messsage has been updated to reflect this.

##### Components

* [OpenTelemetry Collector - v0.111.0](https://redirect.github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.111.0)
* [OpenTelemetry Contrib - v0.111.0](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.111.0)
* [Java auto-instrumentation - v1.33.5](https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.33.5)
* [.NET auto-instrumentation - v1.2.0](https://redirect.github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.2.0)
* [Node.JS - v0.53.0](https://redirect.github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.53.0)
* [Python - v0.48b0](https://redirect.github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.48b0)
* [Go - v0.15.0-alpha](https://redirect.github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.15.0-alpha)
* [ApacheHTTPD - 1.0.4](https://redirect.github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
* [Nginx - 1.0.4](https://redirect.github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)

`v0.111.0`

Compare Source

💡 Enhancements 💡

auto-instrumentation: set OTEL_LOGS_EXPORTER env var to otlp in python instrumentation (#3330)
collector: Expose the Collector telemetry endpoint by default. (#3361)

The collector v0.111.0 changes the default binding of the telemetry metrics endpoint from 0.0.0.0 to localhost.
To avoid any disruption we fallback to 0.0.0.0:{PORT} as default address.
Details can be found here: opentelemetry-collector#11251
auto-instrumentation: Add support for specifying exporter TLS certificates in auto-instrumentation. (#3338)

Now Instrumentation CR supports specifying TLS certificates for exporter:
```
spec:
  exporter:
    endpoint: https://otel-collector:4317
    tls:
      secretName: otel-tls-certs
      configMapName: otel-ca-bundle
```

otel-ca-bundle

    ca_file: ca.crt

present in otel-tls-certs

    cert_file: tls.crt

present in otel-tls-certs

    key_file: tls.key


* Propagating secrets across namespaces can be done with https://github.com/EmberStack/kubernetes-reflector or https://github.com/zakkg3/ClusterSecret
* Restarting workloads on certificate renewal can be done with https://github.com/stakater/Reloader or https://github.com/wave-k8s/wave

- `collector`: Add native sidecar injection behind a feature gate which is disabled by default. (#&#8203;2376)

Native sidecars are supported since Kubernetes version `1.28` and are availabe by default since `1.29`.
To use native sidecars on Kubernetes v1.28 make sure the "SidecarContainers" feature gate on kubernetes is enabled.
If native sidecars are available, the operator can be advised to use them by adding
the `--feature-gates=operator.sidecarcontainers.native` to the Operator args.
In the future this may will become availabe as deployment mode on the Collector CR. See [#&#8203;3356](https://redirect.github.com/open-telemetry/opentelemetry-operator/issues/3356)

- `target allocator, collector`: Enable mTLS between the TA and collector for passing secrets in the scrape_config securely (#&#8203;1669)

This change enables mTLS between the collector and the target allocator (requires cert-manager).
This is necessary for passing secrets securely from the TA to the collector for scraping endpoints that have authentication. Use the `operator.targetallocator.mtls` to enable this feature. See the target allocator [documentation](https://redirect.github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator#service--pod-monitor-endpoint-credentials) for more details.

##### 🧰 Bug fixes 🧰

- `collector-webhook`: Fixed validation of `stabilizationWindowSeconds` in autoscaler behaviour (#&#8203;3345)

The validation of `stabilizationWindowSeconds` in the `autoscaler.behaviour.scale[Up|Down]` incorrectly rejected 0 as an invalid value.
This has been fixed to ensure that the value is validated correctly (should be >=0 and <=3600) and the error messsage has been updated to reflect this.

##### Components

* [OpenTelemetry Collector - v0.111.0](https://redirect.github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.111.0)
* [OpenTelemetry Contrib - v0.111.0](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.111.0)
* [Java auto-instrumentation - v1.33.5](https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.33.5)
* [.NET auto-instrumentation - v1.2.0](https://redirect.github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.2.0)
* [Node.JS - v0.53.0](https://redirect.github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.53.0)
* [Python - v0.48b0](https://redirect.github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.48b0)
* [Go - v0.15.0-alpha](https://redirect.github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.15.0-alpha)
* [ApacheHTTPD - 1.0.4](https://redirect.github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
* [Nginx - 1.0.4](https://redirect.github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)

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.

…ntelemetry-operator docker tag to v0.113.0

renovate bot requested a review from a team as a code owner October 22, 2024 07:54

renovate bot changed the title ~~chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.111.0~~ chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.112.0 Oct 30, 2024

renovate bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch from 0f8c0b5 to 8f648f4 Compare October 30, 2024 16:11

renovate bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch from 8f648f4 to 0272794 Compare November 8, 2024 20:07

renovate bot changed the title ~~chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.112.0~~ chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator docker tag to v0.113.0 Nov 8, 2024

renovate bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch from 0272794 to 6e09a96 Compare November 14, 2024 09:54

chore(deps): update ghcr.io/open-telemetry/opentelemetry-operator/ope…

5ade6ab

…ntelemetry-operator docker tag to v0.113.0

renovate bot force-pushed the renovate/ghcr.io-open-telemetry-opentelemetry-operator-opentelemetry-operator-0.x branch from 6e09a96 to 5ade6ab Compare November 14, 2024 10:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Oct 22, 2024 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Oct 22, 2024 • edited Loading

Release Notes

v0.113.0

0.113.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

v0.113.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

v0.112.0

0.112.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

v0.112.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

v0.111.0

0.111.0

💡 Enhancements 💡

otel-ca-bundle

present in otel-tls-certs

present in otel-tls-certs

v0.111.0

💡 Enhancements 💡

otel-ca-bundle

present in otel-tls-certs

present in otel-tls-certs

Configuration

renovate bot commented Oct 22, 2024 •

edited

Loading

`v0.113.0`

`v0.113.0`

`v0.112.0`

`v0.112.0`

`v0.111.0`

`v0.111.0`