chore(deps): update otel-operator-source to v0.113.0 #1143

renovate · 2024-03-11T16:11:27Z

This PR contains the following updates:

Package	Update	Change
otel-operator-source	minor	`v0.95.0` -> `v0.113.0`

Release Notes

open-telemetry/opentelemetry-operator (otel-operator-source)

`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.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.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.110.0`

Compare Source

0.110.0

🛑 Breaking changes 🛑

auto-instrumentation: Enable multi instrumentation by default. (#3090)

Starting with this release, the OpenTelemetry Operator now enables multi-instrumentation by default.
This enhancement allows instrumentation of multiple containers in a pod with language-specific configurations.

Key Changes:
- Single Instrumentation (Default Behavior): If no container names are specified using the
  instrumentation.opentelemetry.io/container-names annotation, instrumentation will be applied to the first container in
  the pod spec by default. This only applies when single instrumentation injection is configured.
- Multi-Container Pods: In scenarios where different containers in a pod use distinct technologies, users must specify the
  container(s) for instrumentation using language-specific annotations. Without this specification, the default behavior may
  not work as expected for multi-container environments.
Compatibility:
- Users already utilizing the instrumentation.opentelemetry.io/container-names annotation do not need to take any action.
  Their existing setup will continue to function as before.
- Important: Users who attempt to configure both instrumentation.opentelemetry.io/container-names and language-specific annotations
  (for multi-instrumentation) simultaneously will encounter an error, as this configuration is not supported.
collector: Remove ComponentUseLocalHostAsDefaultHost collector feature gate. (#3306)

This change may break setups where receiver endpoints are not explicitly configured to listen on e.g. 0.0.0.0.
Change #3333 attempts to address this issue for a known set of components.
The operator performs the adjustment for the following receivers:
- otlp
- skywalking
- jaeger
- loki
- opencensus
- zipkin
- tcplog
- udplog
- fluentforward
- statsd
- awsxray/UDP
- carbon
- collectd
- sapm
- signalfx
- splunk_hec
- wavefront

💡 Enhancements 💡

auto-instrumentation, collector: Add a must gather utility to help troubleshoot (#3149)

The new utility is available as part of a new container image.

To use the image in a running OpenShift cluster, you need to run the following command:
```
oc adm must-gather --image=ghcr.io/open-telemetry/opentelemetry-operator/must-gather -- /usr/bin/must-gather --operator-namespace opentelemetry-operator-system
```
See the README for more details.
collector: set default address for all parsed receivers (#3126)

This feature is enabled by default. It can be disabled by specifying
--feature-gates=-operator.collector.default.config.
operator: Use 0.0.0.0 as otlp receiver default address (#3126)
collector: Add flag to disable components when operator runs on FIPS enabled cluster. (#3315)
Flag --fips-disabled-components=receiver.otlp,exporter.otlp,processor.batch,extension.oidc can be used to disable
components when operator runs on FIPS enabled cluster. The operator uses /proc/sys/crypto/fips_enabled to check
if FIPS is enabled.
collector: Improves healthcheck parsing capabilities, allowing for future extensions to configure a healthcheck other than the v1 healthcheck extension. (#3184)
auto-instrumentation: Add support for k8s labels such as app.kubernetes.io/name for resource attributes (#3112)

You can opt-in as follows:
```
apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: my-instrumentation
spec:
  defaults:
    useLabelsForResourceAttributes: true
```
The following labels are supported:
- app.kubernetes.io/name becomes service.name
- app.kubernetes.io/version becomes service.version
- app.kubernetes.io/part-of becomes service.namespace
- app.kubernetes.io/instance becomes service.instance.id

🧰 Bug fixes 🧰

auto-instrumentation: Fix ApacheHttpd, Nginx and SDK injectors to honour their container-names annotations. (#3313)

This is a breaking change if anyone is accidentally using the enablement flag with container names for these 3 injectors.

Components

`v0.109.0`

Compare Source

0.109.0

🚩 Deprecations 🚩

operator: Deprecated label flag and introduced labels-filter flag to align the label filtering with the attribute filtering flag name. The label flag will be removed when #3236 issue is resolved. (#3218)

💡 Enhancements 💡

collector: adds test for memory utilization (#3283)
operator: Added reconciliation errors for webhook events. The webhooks run the manifest generators to check for any errors. (#2399)

Components

`v0.108.0`

Compare Source

0.108.0

💡 Enhancements 💡

auto-instrumentation: set OTEL_EXPORTER_OTLP_PROTOCOL instead of signal specific env vars in python instrumentation (#3165)
collector: Allow autoscaler targetCPUUtilization and TargetMemoryUtilization to be greater than 99 (#3258)
auto-instrumentation: Not ignore the instrumentation.opentelemetry.io/container-names annotation when the multi-instrumentation is enabled (#3090)
operator: Support for Kubernetes 1.31 version. (#3247)
target allocator: introduces the global field in the TA config to allow for setting scrape protocols (#3160)

🧰 Bug fixes 🧰

auto-instrumentation: Fix file copy for NGINX auto-instrumentation for non-root workloads. (#2726)
target allocator: Retrying failed namespace informer creation in promOperator CRD watcher, then exit if creation issue cannot be resolved (#3216)
target allocator: Rollback #3187 (#3242)
This Rollsback 3187 which breaks TargetAllocator config for clusters with custom domains.
auto-instrumentation: Fixes a bug that was preventing auto instrumentation from getting correct images. (#3014)
This PR removes the restriction on the operator to only upgrade manually applied CRDs. This meant
that resources applied by helm were not upgraded at all. The solution was to remove the restriction
we had on querying the label app.kubernetes.io/managed-by=opentelemetry-operator, thereby upgrading
ALL CRDs in the cluster.
collector: Fixes a bug that was preventing upgrade patches from reliably applying. (#3074)
A bug was discovered in the process of testing the PR that was failing to remove the environment
variables introduced in the 0.104.0 upgrade. The fix was to take a deepcopy of the object and update that.
collector: Don't unnecessarily take ownership of PersistentVolumes and PersistentVolumeClaims (#3042)
awsxray-receiver: Switched the protocol of awsxray-receiver to UDP from TCP (#3261)

Components

`v0.107.0`

Compare Source

0.107.0

💡 Enhancements 💡

instrumentation: introduced ability to set Otel resource attributes based on annotations for instrumentation (#2181)

resource.opentelemetry.io/your-key: "your-value"

🧰 Bug fixes 🧰

collector: Fix example for labels-filter startup parameter --label. (#3201)

Components

`v0.106.0`

Compare Source

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

`v0.105.0`

Compare Source

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 🧰

`v0.104.0`

Compare Source

0.104.0

🛑 Breaking changes 🛑

opamp: Adds support for v1beta1 OpenTelemetry Collector API in the OpAMP Bridge (#2985)
This change adds support for the OpAMP Bridge to manage and apply OpenTelemetry Collectors using the v1beta1 API in
the OpAMP Bridge. This change removes support for applying OpenTelemetry Collectors using the v1alpha1 API version.
The v1beta1 API is the latest version of the OpenTelemetry Collector API and is the recommended version for new
deployments.

💡 Enhancements 💡

collector: Since collector version 0.104.0 the collector listens on localhost instead of 0.0.0.0 by default (collector#8510). To avoid breaking changes the component.UseLocalHostAsDefaultHost feature-gate is disabled by the Operator. (#3119)
collector: Changes the default parser to silently fail. (#3133)
collector, target allocator: If the target allocator is enabled, the collector featuregate `confmap.unifyEnvVarExpansion' is disabled. (#3119)
operator: Release leader election lease on exit (#3058)
collector, target allocator, opamp: Enabling PodDnsConfig for OpenTelemetry Collector, TargetAllocator and OpAMPBridge. (#2658)
collector: Make the spec.mode field of the OpenTelemetryCollector Custom Resource (CR) immutable (#3055)
collector: Improves the performance of port and configuration parsing in the operator (#2603)

🧰 Bug fixes 🧰

collector: Fixes a bug where an exporter would cause a port collision (#3124)
collector: Fix deletion issue of otelcol CR by making spec.config.service.pipelines.processors optional (#3075)
This change makes spec.config.service.pipelines.processors in OpenTelemetryCollector CRD optional, aligning with OTel Collector best practices. It resolves deletion issues by providing flexibility in CRD configuration, addressing conflicts between strict validation and practical uses.
Note: Updating the opentelemetrycollectors.opentelemetry.io CRD resource is required.
collector: Allow annotations on service account to prevent infinite reconciliation on OpenShift and creating infinite pull secrets. (#3106)
On OpenShift 4.16 the platform automatically adds an annotation openshift.io/internal-registry-pull-secret-ref: <simplest-collector-dockercfg-jwq66>
to the service account which contains secret name with image pull secret.

Components

`v0.103.0`

Compare Source

0.103.0

💡 Enhancements 💡

collector, target allocator, opamp: Require Go 1.22 for building the operator (#2757)

🧰 Bug fixes 🧰

auto-instrumentation: Fix webserver instrumentation log file name (#2978)

Since webserver instrumentation 1.0.4, the configuration log file has been renamed from appdynamics_sdk_log4cxx.xml.template to opentelemetry_sdk_log4cxx.xml.template. The operator upgraded the webserver instrumentation version but haven't change the configuration file name.
target-allocator: Fixes a bug that didn't automatically create a PDB for a TA with per-node strategy (#2900)

Components

`v0.102.0`

Compare Source

0.102.0

💡 Enhancements 💡

collector: Add usage metrics for the collector (#2829)
This change will add metrics to the OpenTelemetry operator about how the collector is used in the cluster,
it will add the following metrics to the opentelemetry-operator metrics endpoint
opentelemetry_collector_receivers{collector_name="collector_name", namespace="ns", type="otlp"} 1
opentelemetry_collector_exporters{collector_name="collector_name", namespace="ns", type="otlp"} 1
opentelemetry_collector_processors{collector_name="collector_name", namespace="ns", type="otlp"} 1
opentelemetry_collector_connectors{collector_name="collector_name", namespace="ns", type="myconnector"} 0
opentelemetry_collector_info{collector_name="simplest",namespace="default", type="deployment"} 1

🧰 Bug fixes 🧰

collector: Fixes a bug that was preventing regexes from being loaded correctly. Now the filter provide is exactly what's used. (#3007)
This is technically a breaking change if a user relied on the previously broken regex functionality.
This change will actually fix their regex to work where it didn't before. I expect that users would rather their
regexes work than break silently.
collector: Upgrades to 0.102.1 which resolves a CVE in the configgrpc package. See here for more details

Components

`v0.101.0`

Compare Source

0.101.0

💡 Enhancements 💡

operator: Support for Kubernetes 1.30 version. (#2881)
collector: Keep multiple previous versions of the Collector ConfigMap, configurable via the ConfigVersions field. (#2871)
This change introduces a new field in the Collector ConfigMap, ConfigVersions, which allows users to specify the number of previous versions of the Collector ConfigMap to keep. The default value is 1, which means that the current and one previous version of the Collector ConfigMap are kept. By keeping historical versions of the configuration, we ensure that during a config upgrade the previous configuration is still available for running (non-upgraded) pods as well as for rollbacks. If we overwrite the original ConfigMap with the new configuration, any pod which restarts for any reason will get the new configuration, which makes rollouts impossible to control.
collector, target allocator, opamp: Introduces a new feature gate for operator.golang.flags to automatically add the environment variables for GOMAXPROCS and GOMEMLIMIT (#2919, #1456)
A new featuregate operator.golang.flags is added. This featuregate will allow the operator to automatically
set GOMAXPROCS and GOMEMLIMIT equal to the CPU and Memory limit provided respectively for the pod.

Components

`v0.100.1`

Compare Source

0.100.1

💡 Enhancements 💡

target allocator: Refactor allocation strategies (#2928)
The performance of the per-node strategy was massively improved as part of this change.

🧰 Bug fixes 🧰

operator: Fixes an issue where the user can no longer set the webhook port (#2923)

Components

`v0.100.0`

Compare Source

0.100.0

💡 Enhancements 💡

opamp: Add healthy field at collector pool level in opamp bridge heartbeat (#2936)
collector: Add support for readinessProbe on OpenTelemetryCollector CRD. (#2943)
Add support for readinessProbe on OpenTelemetryCollector and its default similar to the already supported livenessProbe.
operator: Enabling new Logs Enconder Configuration parameters. (#268)
operator: Automatically enable RBAC creation if operator SA can create clusterroles and bindings. --create-rbac-permissions flag is noop and deprecated now. (#2588)
target allocator: Added option for creating an mTLS-configured HTTPS server to fetch scrape config with real secret values. (#1669)
The change introduces an option to create an additional HTTPS server with mTLS configuration.
This server is specifically utilized for obtaining the scrape configuration with actual secret values.

🧰 Bug fixes 🧰

collector: Create a Service Monitor for the monitoring service and another one for the collector service when the Prometheus exporter is used. (#2877)
Create a Service Monitor for the collector Service when Prometheus exporter is used. A different Service Monitor is created for the monitoring service.
This helps excluding the headless service (duplicating the metrics collection) and splits responsibilities between the two Service Monitors.
Now, the operator.opentelemetry.io/collector-service-type label is used to differentiate the services.
operator.opentelemetry.io/collector-monitoring-service and operator.opentelemetry.io/collector-headless-service are deprecated now.
target-allocator: Fixed non-expected warnings on TA webhook. (#2685)
collector: Ensure all Prometheus CRDs are installed (#2964)
collector: Cleanup ClusterRoles and ClusterRoleBindings created by the operator (#2938)
The operator uses finalizer on the collector to run the cleanup
collector: Use the k8snode detector instead of kubernetes for the automatic RBAC creation for the resourcedetector (#2833)
collector: When two Collectors are created with the same name but different namespaces, the ClusterRoleBinding created by the first will be overriden by the second one. (#2862)
collector: Fix to reflect changes of OpenTelemetryCollector.spec.nodeSelector in the collector Pods (#2940)
When updating OpenTelemetryCollector.spec.nodeSelector it was not removing previous selector from the final collector pod (Deployment/Daemonset/Statefulset).
collector: Fix of Labels and Annotations filter (#2770)
target allocator: Fix target allocator readiness check (#2903)

Components

`v0.99.0`

Compare Source

0.99.0

🛑 Breaking changes 🛑

operator: change java instrumentation feature gate operator.autoinstrumentation.java into command line flag --enable-java-instrumentation (#2673, #2582)
operator: remove featuregate operator.autoinstrumentation.nodejs. Use command line flag --enable-nodejs-instrumentation instead (#2674)
operator: remove featuregate operator.autoinstrumentation.go. Use command line flag --enable-go-instrumentation instead (#2675)
target allocator: Remove operator.collector.rewritetargetallocator feature flag (#2796)
target allocator: Drop compatibility with older target allocator versions (#1907)
We've made a breaking change to the target allocator configuration in 0.93.0. This change removes operator
compatibility with target allocator versions older than that. Users running more recent target allocator versions
are unaffected.

🚀 New components 🚀

collector: Enable reconciliation of Collector v1beta1 CRD. See CRD changelog for detailed information. (#2620, #1907)
Users are expected to migrate to otelcol.v1beta1.opentelemetry.io.
The support for otelcol.v1alpha1.opentelemetry.io will be removed in the future.
Follow migration guide for upgrading already created collector instances.
After all otelcol.v1alpha1.opentelemetry.io are stored as v1beta1 update the collector CRD to store only v1beta1
kubectl patch customresourcedefinitions opentelemetrycollectors.opentelemetry.io --subresource='status' --type='merge' -p '{"status":{"storedVersions":["v1beta1"]}}'.
Only AllNamespaces install mode is now supported due to the conversion webhook from v1beta1 to v1alpha1.
See OLM docs and
OLM operator groups docs.

💡 Enhancements 💡

collector: Changes metric port logic to use intermediary struct. (#2603)
collector: Remove collector v1alpha1 defaulting and validating webhooks. (#2736)
The functionality was moved to the collector v1beta1 webhooks.

🧰 Bug fixes 🧰

auto-instrumentation: Add attribute service.instance.id while pod is mutated. (#2679)
service.instance.id is expected to be <namespace>.<podName>.<containerName>

But while pod is created it may not have the podName yet at the podMutator webhooks.

This changed to use the env var OTEL_RESOURCE_ATTRIBUTES_POD_NAME which will be present at runtime.
<namespace>.$(OTEL_RESOURCE_ATTRIBUTES_POD_NAME).<containerName>

Making a valid and complete value for service.instance.id to be added.
collector: Fixes a bug that would cause errant rollouts on a non-config related change. (#2899)
collector: resolves a bug that would create a junk selector for the service by merging rather than overriding. (#2873)
target allocator: Fix a metric relabel config unescaping bug (#2867)
If only metric relabel configs were present, without target relabel configs, unescaping wouldn't be applied, leading
to invalid Target Allocator configuration.

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.

Signed-off-by: Curtis John <[email protected]>

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 8ec124f to 123f8e2 Compare April 3, 2024 20:16

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.96.0~~ chore(deps): update otel-operator-source to v0.97.0 Apr 3, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 123f8e2 to 1644b69 Compare April 5, 2024 20:11

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.97.0~~ chore(deps): update otel-operator-source to v0.97.1 Apr 5, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 1644b69 to d941471 Compare April 12, 2024 11:48

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.97.1~~ chore(deps): update otel-operator-source to v0.98.0 Apr 12, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch 2 times, most recently from 0f132af to 9884004 Compare May 1, 2024 10:56

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.98.0~~ chore(deps): update otel-operator-source to v0.99.0 May 1, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch 3 times, most recently from 72f4c85 to 1d0205e Compare May 20, 2024 17:26

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.99.0~~ chore(deps): update otel-operator-source to v0.100.0 May 20, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 1d0205e to c367e07 Compare May 20, 2024 23:23

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.100.0~~ chore(deps): update otel-operator-source to v0.100.1 May 20, 2024

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.100.1~~ chore(deps): update otel-operator-source to v0.101.0 May 29, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch 2 times, most recently from b54429b to b549658 Compare June 2, 2024 23:03

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from b549658 to ea37d4a Compare June 6, 2024 16:07

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.101.0~~ chore(deps): update otel-operator-source to v0.102.0 Jun 6, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from ea37d4a to 8c3fe0a Compare June 12, 2024 03:10

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 8c3fe0a to 80e1efb Compare June 25, 2024 21:28

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.102.0~~ chore(deps): update otel-operator-source to v0.103.0 Jun 25, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 80e1efb to 55df965 Compare July 18, 2024 12:32

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.103.0~~ chore(deps): update otel-operator-source to v0.104.0 Jul 18, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch 2 times, most recently from 782937f to 8816972 Compare July 30, 2024 22:20

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.104.0~~ chore(deps): update otel-operator-source to v0.105.0 Jul 30, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch 2 times, most recently from 37b2ac8 to c32aa68 Compare August 7, 2024 18:02

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.105.0~~ chore(deps): update otel-operator-source to v0.106.0 Aug 7, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from c32aa68 to 70be876 Compare August 15, 2024 19:19

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.106.0~~ chore(deps): update otel-operator-source to v0.107.0 Aug 15, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 70be876 to 43105a9 Compare August 19, 2024 00:29

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 43105a9 to bf43f41 Compare September 5, 2024 18:08

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.107.0~~ chore(deps): update otel-operator-source to v0.108.0 Sep 5, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from bf43f41 to a62357d Compare September 21, 2024 22:26

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.108.0~~ chore(deps): update otel-operator-source to v0.109.0 Sep 21, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from a62357d to 4edfca6 Compare October 9, 2024 17:16

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.109.0~~ chore(deps): update otel-operator-source to v0.110.0 Oct 9, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from 4edfca6 to cce2db6 Compare October 21, 2024 17:26

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.110.0~~ chore(deps): update otel-operator-source to v0.111.0 Oct 21, 2024

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from cce2db6 to e407417 Compare October 30, 2024 17:04

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.111.0~~ chore(deps): update otel-operator-source to v0.112.0 Oct 30, 2024

chore(deps): update otel-operator-source to v0.113.0

505cdba

Signed-off-by: Curtis John <[email protected]>

renovate bot force-pushed the renovate/otel-operator-source-0.x branch from e407417 to 505cdba Compare November 8, 2024 19:45

renovate bot changed the title ~~chore(deps): update otel-operator-source to v0.112.0~~ chore(deps): update otel-operator-source to v0.113.0 Nov 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update otel-operator-source to v0.113.0 #1143

chore(deps): update otel-operator-source to v0.113.0 #1143

renovate bot commented Mar 11, 2024 •

edited

Loading

chore(deps): update otel-operator-source to v0.113.0 #1143

Are you sure you want to change the base?

chore(deps): update otel-operator-source to v0.113.0 #1143

Conversation

renovate bot commented Mar 11, 2024 • edited Loading

Release Notes

0.113.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.112.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.111.0

💡 Enhancements 💡

otel-ca-bundle

present in otel-tls-certs

present in otel-tls-certs

0.110.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.109.0

🚩 Deprecations 🚩

💡 Enhancements 💡

Components

0.108.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.107.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.106.0

🧰 Bug fixes 🧰

Components

0.105.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

0.104.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.103.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.102.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.101.0

💡 Enhancements 💡

Components

0.100.1

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.100.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.99.0

🛑 Breaking changes 🛑

🚀 New components 🚀

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

Configuration

renovate bot commented Mar 11, 2024 •

edited

Loading