Skip to content

Commit ea989fb

Browse files
TylerHelmuthTylerHelmuth
committed
Prepare v0.115.0 release
1 parent 0590057 commit ea989fb

12 files changed

+63
-112
lines changed

‎.chloggen/fix-prometheus-rule-file.yaml

-16
This file was deleted.

‎.chloggen/revert-3379-otel-configmap.yaml

-19
This file was deleted.

‎.chloggen/scrape_config_probe.yaml

-16
This file was deleted.

‎.chloggen/service-extension.yaml

-16
This file was deleted.

‎.chloggen/service-instanc-id-mapping.yaml

-27
This file was deleted.

‎CHANGELOG.md

+40
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,46 @@
22

33
<!-- next version -->
44

5+
## 0.115.0
6+
7+
### 💡 Enhancements 💡
8+
9+
- `collector`: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)
10+
- `collector`: support for creating a service for extensions when ports are specified. (#3460)
11+
12+
### 🧰 Bug fixes 🧰
13+
14+
- `github action`: Add new line character at the end of PrometheusRule file. (#3503)
15+
- `auto-instrumentation`: Reverts PR 3379 which inadvertently broke users setting JAVA_TOOL_OPTIONS (#3463)
16+
Reverts a previous PR which was causing JAVA_TOOL_OPTIONS to not be overriden when
17+
set by users. This was resulting in application crashloopbackoffs for users relying
18+
on java autoinstrumentation.
19+
20+
- `auto-instrumentation`: Remove the mapping of `app.kubernetes.io/instance` to `service.instance.id` (#3495)
21+
Technically, this is a breaking change, but we regard it as a bug fix because the previous behavior was incorrect.
22+
23+
if you did have multiple container instrumentation and use `app.kubernetes.io/instance` to set the `service.instance.id`,
24+
you will now see multiple instances in the UI - which is the correct behavior.
25+
26+
You can still use the attribute `resource.opentelemetry.io/service.instance.id` to set the `service.instance.id`,
27+
which will be shared across all containers in the pod - but this is not recommended for multiple container instrumentation instances.
28+
29+
Refer to the [semantic conventions](https://opentelemetry.io/docs/specs/semconv/resource/#service-experimental)
30+
for more information.
31+
32+
33+
### Components
34+
35+
* [OpenTelemetry Collector - v0.115.1](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.115.1)
36+
* [OpenTelemetry Contrib - v0.115.1](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.115.1)
37+
* [Java auto-instrumentation - v1.33.5](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.33.5)
38+
* [.NET auto-instrumentation - v1.2.0](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.2.0)
39+
* [Node.JS - v0.53.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.53.0)
40+
* [Python - v0.48b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.48b0)
41+
* [Go - v0.19.0-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.19.0-alpha)
42+
* [ApacheHTTPD - 1.0.4](https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
43+
* [Nginx - 1.0.4](https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
44+
545
## 0.114.0
646

747
### 💡 Enhancements 💡

‎RELEASE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -44,10 +44,10 @@ The operator should be released within a week after the [OpenTelemetry collector
4444

4545
| Version | Release manager |
4646
|----------|-----------------|
47-
| v0.115.0 | @TylerHelmuth |
4847
| v0.116.0 | @jaronoff97 |
4948
| v0.117.0 | @iblancasa |
5049
| v0.118.0 | @frzifus |
5150
| v0.119.0 | @yuriolisa |
5251
| v0.120.0 | @pavolloffay |
5352
| v0.121.0 | @swiatekm |
53+
| v0.122.0 | @TylerHelmuth |

‎bundle/community/manifests/opentelemetry-operator.clusterserviceversion.yaml

+4-4
Original file line numberDiff line numberDiff line change
@@ -99,13 +99,13 @@ metadata:
9999
categories: Logging & Tracing,Monitoring
100100
certified: "false"
101101
containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
102-
createdAt: "2024-11-27T11:54:33Z"
102+
createdAt: "2024-12-10T17:11:22Z"
103103
description: Provides the OpenTelemetry components, including the Collector
104104
operators.operatorframework.io/builder: operator-sdk-v1.29.0
105105
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
106106
repository: github.com/open-telemetry/opentelemetry-operator
107107
support: OpenTelemetry Community
108-
name: opentelemetry-operator.v0.114.0
108+
name: opentelemetry-operator.v0.115.0
109109
namespace: placeholder
110110
spec:
111111
apiservicedefinitions: {}
@@ -483,7 +483,7 @@ spec:
483483
valueFrom:
484484
fieldRef:
485485
fieldPath: spec.serviceAccountName
486-
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.114.0
486+
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.115.0
487487
livenessProbe:
488488
httpGet:
489489
path: /healthz
@@ -591,7 +591,7 @@ spec:
591591
minKubeVersion: 1.23.0
592592
provider:
593593
name: OpenTelemetry Community
594-
version: 0.114.0
594+
version: 0.115.0
595595
webhookdefinitions:
596596
- admissionReviewVersions:
597597
- v1alpha1

‎bundle/openshift/manifests/opentelemetry-operator.clusterserviceversion.yaml

+4-4
Original file line numberDiff line numberDiff line change
@@ -99,13 +99,13 @@ metadata:
9999
categories: Logging & Tracing,Monitoring
100100
certified: "false"
101101
containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
102-
createdAt: "2024-11-27T11:54:33Z"
102+
createdAt: "2024-12-10T17:11:31Z"
103103
description: Provides the OpenTelemetry components, including the Collector
104104
operators.operatorframework.io/builder: operator-sdk-v1.29.0
105105
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
106106
repository: github.com/open-telemetry/opentelemetry-operator
107107
support: OpenTelemetry Community
108-
name: opentelemetry-operator.v0.114.0
108+
name: opentelemetry-operator.v0.115.0
109109
namespace: placeholder
110110
spec:
111111
apiservicedefinitions: {}
@@ -487,7 +487,7 @@ spec:
487487
valueFrom:
488488
fieldRef:
489489
fieldPath: spec.serviceAccountName
490-
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.114.0
490+
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.115.0
491491
livenessProbe:
492492
httpGet:
493493
path: /healthz
@@ -606,7 +606,7 @@ spec:
606606
minKubeVersion: 1.23.0
607607
provider:
608608
name: OpenTelemetry Community
609-
version: 0.114.0
609+
version: 0.115.0
610610
webhookdefinitions:
611611
- admissionReviewVersions:
612612
- v1alpha1

‎config/manager/kustomization.yaml

+6-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
11
resources:
22
- manager.yaml
3-
3+
apiVersion: kustomize.config.k8s.io/v1beta1
4+
kind: Kustomization
5+
images:
6+
- name: controller
7+
newName: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
8+
newTag: 0.115.0

‎docs/compatibility.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,9 @@ Generally speaking, these are backwards compatible, but specific features requir
4545
The OpenTelemetry Operator _might_ work on versions outside of the given range, but when opening new issues, please make sure to test your scenario on a supported version.
4646

4747
| OpenTelemetry Operator | Kubernetes | Cert-Manager | Prometheus-Operator |
48-
|------------------------|----------------| ------------ |---------------------|
48+
|------------------------|----------------|--------------|---------------------|
49+
| v0.115.0 | v1.23 to v1.31 | v1 | v0.76.0 |
50+
| v0.114.0 | v1.23 to v1.31 | v1 | v0.76.0 |
4951
| v0.113.0 | v1.23 to v1.31 | v1 | v0.76.0 |
5052
| v0.112.0 | v1.23 to v1.31 | v1 | v0.76.0 |
5153
| v0.111.0 | v1.23 to v1.31 | v1 | v0.76.0 |
@@ -68,8 +70,6 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,
6870
| v0.94.0 | v1.23 to v1.29 | v1 | v0.71.0 |
6971
| v0.93.0 | v1.23 to v1.29 | v1 | v0.71.0 |
7072
| v0.92.0 | v1.23 to v1.29 | v1 | v0.71.0 |
71-
| v0.91.0 | v1.23 to v1.29 | v1 | v0.70.0 |
72-
| v0.90.0 | v1.23 to v1.28 | v1 | v0.69.1 |
7373

7474
[kubernetes_releases]: https://kubernetes.io/releases/
7575
[openshift_support]: https://access.redhat.com/support/policy/updates/openshift

‎versions.txt

+5-5
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,16 @@
22
# by default with the OpenTelemetry Operator. This would usually be the latest
33
# stable OpenTelemetry version. When you update this file, make sure to update the
44
# the docs as well.
5-
opentelemetry-collector=0.114.0
5+
opentelemetry-collector=0.115.1
66

77
# Represents the current release of the OpenTelemetry Operator.
8-
operator=0.114.0
8+
operator=0.115.0
99

1010
# Represents the current release of the Target Allocator.
11-
targetallocator=0.114.0
11+
targetallocator=0.115.0
1212

1313
# Represents the current release of the Operator OpAMP Bridge.
14-
operator-opamp-bridge=0.114.0
14+
operator-opamp-bridge=0.115.0
1515

1616
# Represents the current release of Java instrumentation.
1717
# Should match autoinstrumentation/java/version.txt
@@ -30,7 +30,7 @@ autoinstrumentation-python=0.48b0
3030
autoinstrumentation-dotnet=1.2.0
3131

3232
# Represents the current release of Go instrumentation.
33-
autoinstrumentation-go=v0.17.0-alpha
33+
autoinstrumentation-go=v0.19.0-alpha
3434

3535
# Represents the current release of Apache HTTPD instrumentation.
3636
# Should match autoinstrumentation/apache-httpd/version.txt

0 commit comments

Comments
 (0)