[chore] Prepare v0.115.0 release (#3533)

* Prepare v0.115.0 release * Update config/manager/kustomization.yaml Co-authored-by: Mikołaj Świątek <[email protected]> * Revert kustomize back to main --------- Co-authored-by: Mikołaj Świątek <[email protected]>
open-telemetry · Dec 11, 2024 · ea70b49 · ea70b49
1 parent 3510993
commit ea70b49
Show file tree

Hide file tree

Showing 11 changed files with 57 additions and 111 deletions.
diff --git a/.chloggen/fix-prometheus-rule-file.yaml b/.chloggen/fix-prometheus-rule-file.yaml
diff --git a/.chloggen/revert-3379-otel-configmap.yaml b/.chloggen/revert-3379-otel-configmap.yaml
diff --git a/.chloggen/scrape_config_probe.yaml b/.chloggen/scrape_config_probe.yaml
diff --git a/.chloggen/service-extension.yaml b/.chloggen/service-extension.yaml
diff --git a/.chloggen/service-instanc-id-mapping.yaml b/.chloggen/service-instanc-id-mapping.yaml
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,46 @@
 
 <!-- next version -->
 
+## 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 of `app.kubernetes.io/instance` to `service.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/instance` to set the `service.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.id` to set the `service.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](https://opentelemetry.io/docs/specs/semconv/resource/#service-experimental) 
+  for more information.
+
+
+### Components
+
+* [OpenTelemetry Collector - v0.115.1](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.115.1)
+* [OpenTelemetry Contrib - v0.115.1](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.115.1)
+* [Java auto-instrumentation - v1.33.5](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.33.5)
+* [.NET auto-instrumentation - v1.2.0](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.2.0)
+* [Node.JS - v0.53.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.53.0)
+* [Python - v0.48b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.48b0)
+* [Go - v0.19.0-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.19.0-alpha)
+* [ApacheHTTPD - 1.0.4](https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
+* [Nginx - 1.0.4](https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.4)
+
 ## 0.114.0
 
 ### 💡 Enhancements 💡

diff --git a/RELEASE.md b/RELEASE.md
@@ -44,10 +44,10 @@ The operator should be released within a week after the [OpenTelemetry collector
 
 | Version  | Release manager |
 |----------|-----------------|
-| v0.115.0 | @TylerHelmuth   |
 | v0.116.0 | @jaronoff97     |
 | v0.117.0 | @iblancasa      |
 | v0.118.0 | @frzifus        |
 | v0.119.0 | @yuriolisa      |
 | v0.120.0 | @pavolloffay    |
 | v0.121.0 | @swiatekm       |
+| v0.122.0 | @TylerHelmuth   |
diff --git a/bundle/community/manifests/opentelemetry-operator.clusterserviceversion.yaml b/bundle/community/manifests/opentelemetry-operator.clusterserviceversion.yaml
@@ -99,13 +99,13 @@ metadata:
     categories: Logging & Tracing,Monitoring
     certified: "false"
     containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
-    createdAt: "2024-11-27T11:54:33Z"
+    createdAt: "2024-12-10T17:11:22Z"
     description: Provides the OpenTelemetry components, including the Collector
     operators.operatorframework.io/builder: operator-sdk-v1.29.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: github.com/open-telemetry/opentelemetry-operator
     support: OpenTelemetry Community
-  name: opentelemetry-operator.v0.114.0
+  name: opentelemetry-operator.v0.115.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -483,7 +483,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: spec.serviceAccountName
-                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.114.0
+                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.115.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -591,7 +591,7 @@ spec:
   minKubeVersion: 1.23.0
   provider:
     name: OpenTelemetry Community
-  version: 0.114.0
+  version: 0.115.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1alpha1

diff --git a/bundle/openshift/manifests/opentelemetry-operator.clusterserviceversion.yaml b/bundle/openshift/manifests/opentelemetry-operator.clusterserviceversion.yaml
@@ -99,13 +99,13 @@ metadata:
     categories: Logging & Tracing,Monitoring
     certified: "false"
     containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
-    createdAt: "2024-11-27T11:54:33Z"
+    createdAt: "2024-12-10T17:11:31Z"
     description: Provides the OpenTelemetry components, including the Collector
     operators.operatorframework.io/builder: operator-sdk-v1.29.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: github.com/open-telemetry/opentelemetry-operator
     support: OpenTelemetry Community
-  name: opentelemetry-operator.v0.114.0
+  name: opentelemetry-operator.v0.115.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -487,7 +487,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: spec.serviceAccountName
-                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.114.0
+                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.115.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -606,7 +606,7 @@ spec:
   minKubeVersion: 1.23.0
   provider:
     name: OpenTelemetry Community
-  version: 0.114.0
+  version: 0.115.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1alpha1

diff --git a/docs/compatibility.md b/docs/compatibility.md
@@ -45,7 +45,9 @@ Generally speaking, these are backwards compatible, but specific features requir
 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.
 
 | OpenTelemetry Operator | Kubernetes     | Cert-Manager | Prometheus-Operator |
-|------------------------|----------------| ------------ |---------------------|
+|------------------------|----------------|--------------|---------------------|
+| v0.115.0               | v1.23 to v1.31 | v1           | v0.76.0             |
+| v0.114.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | v0.113.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | v0.112.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | 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,
 | v0.94.0                | v1.23 to v1.29 | v1           | v0.71.0             |
 | v0.93.0                | v1.23 to v1.29 | v1           | v0.71.0             |
 | v0.92.0                | v1.23 to v1.29 | v1           | v0.71.0             |
-| v0.91.0                | v1.23 to v1.29 | v1           | v0.70.0             |
-| v0.90.0                | v1.23 to v1.28 | v1           | v0.69.1             |
 
 [kubernetes_releases]: https://kubernetes.io/releases/
 [openshift_support]: https://access.redhat.com/support/policy/updates/openshift

diff --git a/versions.txt b/versions.txt
@@ -2,16 +2,16 @@
 # by default with the OpenTelemetry Operator. This would usually be the latest
 # stable OpenTelemetry version. When you update this file, make sure to update the
 # the docs as well.
-opentelemetry-collector=0.114.0
+opentelemetry-collector=0.115.1
 
 # Represents the current release of the OpenTelemetry Operator.
-operator=0.114.0
+operator=0.115.0
 
 # Represents the current release of the Target Allocator.
-targetallocator=0.114.0
+targetallocator=0.115.0
 
 # Represents the current release of the Operator OpAMP Bridge.
-operator-opamp-bridge=0.114.0
+operator-opamp-bridge=0.115.0
 
 # Represents the current release of Java instrumentation.
 # Should match autoinstrumentation/java/version.txt
@@ -30,7 +30,7 @@ autoinstrumentation-python=0.48b0
 autoinstrumentation-dotnet=1.2.0
 
 # Represents the current release of Go instrumentation.
-autoinstrumentation-go=v0.17.0-alpha
+autoinstrumentation-go=v0.19.0-alpha
 
 # Represents the current release of Apache HTTPD instrumentation.
 # Should match autoinstrumentation/apache-httpd/version.txt