Prepare release v0.79.0 (#1816)

* Prepare release v0.79.0 Signed-off-by: Pavol Loffay <[email protected]> * Update Signed-off-by: Pavol Loffay <[email protected]> * Update Signed-off-by: Pavol Loffay <[email protected]> * Update Signed-off-by: Pavol Loffay <[email protected]> --------- Signed-off-by: Pavol Loffay <[email protected]>
open-telemetry · Jun 8, 2023 · 4534a6b · 4534a6b
1 parent d6ed973
commit 4534a6b
Show file tree

Hide file tree

Showing 9 changed files with 35 additions and 76 deletions.
diff --git a/.chloggen/1736-add-service-version-injection.yaml b/.chloggen/1736-add-service-version-injection.yaml
diff --git a/.chloggen/collector-shown-version-is-incorrect-after-upgrade.yaml b/.chloggen/collector-shown-version-is-incorrect-after-upgrade.yaml
diff --git a/.chloggen/improve-crd-status.yaml b/.chloggen/improve-crd-status.yaml
diff --git a/.chloggen/read_env_vars_for_nodejs_autoinstrumentation.yaml b/.chloggen/read_env_vars_for_nodejs_autoinstrumentation.yaml
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -3,6 +3,30 @@ Changes by Version
 
 <!-- next version -->
 
+## 0.79.0
+
+### 💡 Enhancements 💡
+
+- `nodejs autoinstrumentation`: Prometheus metric exporter support for nodejs autoinstrumentation (#1798)
+- `operator`: Add service version injection (#1670)
+  Adds the ability to inject the service version into the environment of the instrumented application.
+- `operator`: Added readyReplicas field to the status section and added Current,Desired and Image to the get operation. (#1355)
+
+### 🧰 Bug fixes 🧰
+
+- `operator`: The OpenTelemetry Collector version is not shown properly in the status field if no upgrade routines are performed. (#1802)
+
+### Components
+
+* [OpenTelemetry Collector - v0.79.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.79.0)
+* [OpenTelemetry Contrib - v0.79.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.79.0)
+* [Java auto-instrumentation - 1.26.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.26.0)
+* [.NET auto-instrumentation - 0.7.0](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v0.7.0)
+* [Node.JS - 0.39.1](https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-node-v0.39.1)
+* [Python - 0.39b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.39b0)
+* [Go - 0.2.1-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.2.1-alpha)
+* [ApacheHTTPD - 1.0.2](https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.2)
+
 ## 0.78.0
 
 ### 💡 Enhancements 💡

diff --git a/README.md b/README.md
@@ -571,6 +571,7 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,
 
 | OpenTelemetry Operator | Kubernetes           | Cert-Manager        |
 |------------------------|----------------------|---------------------|
+| v0.79.0                | v1.19 to v1.27       | v1                  |
 | v0.78.0                | v1.19 to v1.27       | v1                  |
 | v0.77.0                | v1.19 to v1.26       | v1                  |
 | v0.76.1                | v1.19 to v1.26       | v1                  |
@@ -593,7 +594,6 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,
 | v0.58.0                | v1.19 to v1.24       | v1                  |
 | v0.57.2                | v1.19 to v1.24       | v1                  |
 | v0.56.0                | v1.19 to v1.24       | v1                  |
-| v0.55.0                | v1.19 to v1.24       | v1                  |
 
 
 ## Contributing and Developing

diff --git a/RELEASE.md b/RELEASE.md
@@ -5,7 +5,7 @@ Steps to release a new version of the OpenTelemetry Operator:
 1. Change the `versions.txt`, so that it lists the target version of the OpenTelemetry Collector (operand), and the desired version for the target allocator and the operator. The `major.minor` should typically match, with the patch portion being possibly different.
 2. Change the `autoinstrumentation-*` versions in `versions.txt` as per the latest supported versions in `autoinstrumentation/`. 
 3. Run `make bundle USER=open-telemetry VERSION=0.38.0`, using the version that will be released.
-4. Change the compatibility matrix in the readme file, using the OpenTelemetry Operator version to be released and the current latest Kubernetes version as the latest supported version.
+4. Change the compatibility matrix in the [readme](./README.md) file, using the OpenTelemetry Operator version to be released and the current latest Kubernetes version as the latest supported version.
 5. Add the changes to the changelog. Manually add versions of all operator components.
 6. Check the OpenTelemetry Collector's changelog and ensure migration steps are present in `pkg/collector/upgrade`
 7. Once the changes above are merged and available in `main`, tag it with the desired version, prefixed with `v`: `v0.38.0`
@@ -38,9 +38,9 @@ The operator should be released within a week after the [OpenTelemetry collector
 
 | Version | Release manager |
 |---------|-----------------|
-| v0.79.0 | @pavolloffay    |
 | v0.80.0 | @VineethReddy02 |
 | v0.81.0 | @TylerHelmuth   |
 | v0.82.0 | @frzifus        |
 | v0.83.0 | @yuriolisa      |
 | v0.84.0 | @jaronoff97     |
+| v0.85.0 | @pavolloffay    |
diff --git a/bundle/manifests/opentelemetry-operator.clusterserviceversion.yaml b/bundle/manifests/opentelemetry-operator.clusterserviceversion.yaml
@@ -31,13 +31,13 @@ metadata:
     categories: Logging & Tracing
     certified: "false"
     containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
-    createdAt: "2023-06-01T18:31:31Z"
+    createdAt: "2023-06-08T08:15:18Z"
     description: Provides the OpenTelemetry components, including the Collector
     operators.operatorframework.io/builder: operator-sdk-v1.27.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: github.com/open-telemetry/opentelemetry-operator
     support: OpenTelemetry Community
-  name: opentelemetry-operator.v0.78.0
+  name: opentelemetry-operator.v0.79.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -308,7 +308,7 @@ spec:
                 - --zap-log-level=info
                 - --zap-time-encoding=rfc3339nano
                 - --feature-gates=+operator.autoinstrumentation.go
-                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.78.0
+                image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.79.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -415,7 +415,7 @@ spec:
   maturity: alpha
   provider:
     name: OpenTelemetry Community
-  version: 0.78.0
+  version: 0.79.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1

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.78.0
+opentelemetry-collector=0.79.0
 
 # Represents the current release of the OpenTelemetry Operator.
-operator=0.78.0
+operator=0.79.0
 
 # Represents the current release of the Target Allocator.
-targetallocator=0.78.0
+targetallocator=0.79.0
 
 # Represents the current release of the Operator OpAMP Bridge.
-operator-opamp-bridge=0.78.0
+operator-opamp-bridge=0.79.0
 
 # Represents the current release of Java instrumentation.
 # Should match autoinstrumentation/java/version.txt