prepare release v0.111.0

CHANGELOG.md

@@ -2,6 +2,73 @@
 
 <!-- next version -->
 
+## 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](https://github.com/open-telemetry/opentelemetry-collector/pull/11251)
+
+
+- `auto-instrumentation`: Add support for specifying exporter TLS certificates in auto-instrumentation. (#3338)
+
+  Now Instrumentation CR supports specifying TLS certificates for exporter:
+  ```yaml
+  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. (#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 [#3356](https://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 (#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://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 (#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://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.111.0)
+* [OpenTelemetry Contrib - v0.111.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.111.0)
+* [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.15.0-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.15.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.110.0
 
 ### 🛑 Breaking changes 🛑

README.md

@@ -813,6 +813,7 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,
 
 | OpenTelemetry Operator | Kubernetes     | Cert-Manager | Prometheus-Operator |
 |------------------------|----------------| ------------ |---------------------|
+| v0.111.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | v0.110.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | v0.109.0               | v1.23 to v1.31 | v1           | v0.76.0             |
 | v0.108.0               | v1.23 to v1.31 | v1           | v0.76.0             |
@@ -836,7 +837,6 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,
 | v0.90.0                | v1.23 to v1.28 | v1           | v0.69.1             |
 | v0.89.0                | v1.23 to v1.28 | v1           | v0.69.1             |
 | v0.88.0                | v1.23 to v1.28 | v1           | v0.68.0             |
-| v0.87.0                | v1.23 to v1.28 | v1           | v0.68.0             |
 
 ## Contributing and Developing
 

RELEASE.md

@@ -44,10 +44,10 @@ The operator should be released within a week after the [OpenTelemetry collector
 
 | Version  | Release manager |
 |----------|-----------------|
-| v0.111.0 | @frzifus        |
 | v0.112.0 | @yuriolisa      |
 | v0.113.0 | @pavolloffay    |
 | v0.114.0 | @TylerHelmuth   |
 | v0.115.0 | @jaronoff97     |
 | v0.116.0 | @swiatekm       |
 | v0.117.0 | @iblancasa      |
+| v0.118.0 | @frzifus        |

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

@@ -105,7 +105,7 @@ metadata:
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: github.com/open-telemetry/opentelemetry-operator
     support: OpenTelemetry Community
-  name: opentelemetry-operator.v0.110.0
+  name: opentelemetry-operator.v0.111.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -481,7 +481,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: spec.serviceAccountName
-                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.110.0
+                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.111.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -589,7 +589,7 @@ spec:
   minKubeVersion: 1.23.0
   provider:
     name: OpenTelemetry Community
-  version: 0.110.0
+  version: 0.111.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1alpha1

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

@@ -105,7 +105,7 @@ metadata:
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: github.com/open-telemetry/opentelemetry-operator
     support: OpenTelemetry Community
-  name: opentelemetry-operator.v0.110.0
+  name: opentelemetry-operator.v0.111.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -485,7 +485,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: spec.serviceAccountName
-                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.110.0
+                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.111.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -593,7 +593,7 @@ spec:
   minKubeVersion: 1.23.0
   provider:
     name: OpenTelemetry Community
-  version: 0.110.0
+  version: 0.111.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1alpha1

config/manager/kustomization.yaml

@@ -1,2 +1,3 @@
 resources:
 - manager.yaml
+

versions.txt

@@ -2,24 +2,24 @@
 # 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.110.0
+opentelemetry-collector=0.111.0
 
 # Represents the current release of the OpenTelemetry Operator.
-operator=0.110.0
+operator=0.111.0
 
 # Represents the current release of the Target Allocator.
-targetallocator=0.110.0
+targetallocator=0.111.0
 
 # Represents the current release of the Operator OpAMP Bridge.
-operator-opamp-bridge=0.110.0
+operator-opamp-bridge=0.111.0
 
 # Represents the current release of Java instrumentation.
 # Should match autoinstrumentation/java/version.txt
 autoinstrumentation-java=1.33.5
 
 # Represents the current release of NodeJS instrumentation.
 # Should match value in autoinstrumentation/nodejs/package.json
-autoinstrumentation-nodejs=0.52.1
+autoinstrumentation-nodejs=0.53.0
 
 # Represents the current release of Python instrumentation.
 # Should match value in autoinstrumentation/python/requirements.txt
@@ -30,7 +30,7 @@ autoinstrumentation-python=0.48b0
 autoinstrumentation-dotnet=1.2.0
 
 # Represents the current release of Go instrumentation.
-autoinstrumentation-go=v0.14.0-alpha
+autoinstrumentation-go=v0.15.0-alpha
 
 # Represents the current release of Apache HTTPD instrumentation.
 # Should match autoinstrumentation/apache-httpd/version.txt