Skip to content

Prepare release 0.106.0 #3202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 7, 2024
Merged

Prepare release 0.106.0 #3202

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
680e608
Prepare release 0.106.0
pavolloffay Aug 7, 2024
bb028a6
Fix
pavolloffay Aug 7, 2024
8ff4291
Fix
pavolloffay Aug 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions .chloggen/3189-openshift-dashboard-differentiate-otelcols.yaml
View file
Open in desktop

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/3196-openshift-dashboard-list-wrong-namespaces.yaml
View file
Open in desktop

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/fix-pdb-defaulting-logic.yaml
View file
Open in desktop

This file was deleted.

20 changes: 0 additions & 20 deletions .chloggen/fix-ta-with-proxy.yaml
View file
Open in desktop

This file was deleted.

27 changes: 27 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,33 @@

<!-- next version -->

## 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

* [OpenTelemetry Collector - v0.106.1](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.106.1)
Copy link
Member Author

@pavolloffay pavolloffay Aug 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iblancasa

service: Update all metrics to include otelcol_ prefix to ensure consistency across OTLP and Prometheus metrics (open-telemetry/opentelemetry-collector#9759)

https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.106.0

Could you please check if it affects the OCP dashboard?

Copy link
Contributor

@iblancasa iblancasa Aug 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the metrics used for the dashboard included the otelcol_ prefix before.

* [OpenTelemetry Contrib - v0.106.1](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.106.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.52.1](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.52.1)
* [Python - v0.47b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.47b0)
* [Go - v0.14.0-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.14.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.105.0

### 💡 Enhancements 💡
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -739,6 +739,7 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,

| OpenTelemetry Operator | Kubernetes | Cert-Manager | Prometheus-Operator |
|------------------------|----------------| ------------ |---------------------|
| v0.106.0 | v1.23 to v1.30 | v1 | v0.75.0 |
| v0.105.0 | v1.23 to v1.30 | v1 | v0.74.0 |
| v0.104.0 | v1.23 to v1.30 | v1 | v0.74.0 |
| v0.103.0 | v1.23 to v1.30 | v1 | v0.74.0 |
Expand All @@ -761,7 +762,6 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,
| v0.86.0 | v1.23 to v1.28 | v1 | v0.68.0 |
| v0.85.0 | v1.19 to v1.28 | v1 | v0.67.1 |
| v0.84.0 | v1.19 to v1.28 | v1 | v0.67.1 |
| v0.83.0 | v1.19 to v1.27 | v1 | v0.67.1 |

## Contributing and Developing

Expand Down
6 changes: 3 additions & 3 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Steps to release a new version of the OpenTelemetry Operator:
- OpenTelemetry Collector should be the latest collector version. The `major.minor` should typically match, with the patch portion being possibly different.
- The `autoinstrumentation-*` versions should match the latest supported versions in `autoinstrumentation/`.
> [!WARNING]
> DO NOT BUMP JAVA PAST `1.32.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
> DO NOT BUMP JAVA PAST `1.X.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
1. Check if the compatible OpenShift versions are updated in the `Makefile`.
1. Update the bundle by running `make bundle VERSION=$VERSION`.
1. 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. Remove the oldest entry.
Expand Down Expand Up @@ -44,9 +44,9 @@ The operator should be released within a week after the [OpenTelemetry collector

| Version | Release manager |
|----------|-----------------|
| v0.106.0 | @pavolloffay |
| v0.107.0 | @TylerHelmuth |
| v0.108.0 | @jaronoff97 |
| v0.109.0 | @swiatekm |
| v0.110.0 | @frzifus |
| v0.111.0 | @yuriolisa |
| v0.111.0 | @yuriolisa |
| v0.112.0 | @pavolloffay |
8 changes: 4 additions & 4 deletions bundle/community/manifests/opentelemetry-operator.clusterserviceversion.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,13 +99,13 @@ metadata:
categories: Logging & Tracing,Monitoring
certified: "false"
containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
createdAt: "2024-07-25T10:31:46Z"
createdAt: "2024-08-07T08:29:24Z"
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.105.0
name: opentelemetry-operator.v0.106.0
namespace: placeholder
spec:
apiservicedefinitions: {}
Expand Down Expand Up @@ -504,7 +504,7 @@ spec:
valueFrom:
fieldRef:
fieldPath: spec.serviceAccountName
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.105.0
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.106.0
livenessProbe:
httpGet:
path: /healthz
Expand Down Expand Up @@ -612,7 +612,7 @@ spec:
minKubeVersion: 1.23.0
provider:
name: OpenTelemetry Community
version: 0.105.0
version: 0.106.0
webhookdefinitions:
- admissionReviewVersions:
- v1alpha1
Expand Down
8 changes: 4 additions & 4 deletions bundle/openshift/manifests/opentelemetry-operator.clusterserviceversion.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,13 +99,13 @@ metadata:
categories: Logging & Tracing,Monitoring
certified: "false"
containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
createdAt: "2024-07-25T10:31:56Z"
createdAt: "2024-08-07T08:29:28Z"
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.105.0
name: opentelemetry-operator.v0.106.0
namespace: placeholder
spec:
apiservicedefinitions: {}
Expand Down Expand Up @@ -508,7 +508,7 @@ spec:
valueFrom:
fieldRef:
fieldPath: spec.serviceAccountName
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.105.0
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.106.0
livenessProbe:
httpGet:
path: /healthz
Expand Down Expand Up @@ -616,7 +616,7 @@ spec:
minKubeVersion: 1.23.0
provider:
name: OpenTelemetry Community
version: 0.105.0
version: 0.106.0
webhookdefinitions:
- admissionReviewVersions:
- v1alpha1
Expand Down
12 changes: 6 additions & 6 deletions versions.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.105.0
opentelemetry-collector=0.106.1

# Represents the current release of the OpenTelemetry Operator.
operator=0.105.0
operator=0.106.0

# Represents the current release of the Target Allocator.
targetallocator=0.105.0
targetallocator=0.106.0

# Represents the current release of the Operator OpAMP Bridge.
operator-opamp-bridge=0.105.0
operator-opamp-bridge=0.106.0

# Represents the current release of Java instrumentation.
# Should match autoinstrumentation/java/version.txt
Expand All @@ -23,14 +23,14 @@ autoinstrumentation-nodejs=0.52.1

# Represents the current release of Python instrumentation.
# Should match value in autoinstrumentation/python/requirements.txt
autoinstrumentation-python=0.46b0
autoinstrumentation-python=0.47b0

# Represents the current release of DotNet instrumentation.
# Should match autoinstrumentation/dotnet/version.txt
autoinstrumentation-dotnet=1.2.0

# Represents the current release of Go instrumentation.
autoinstrumentation-go=v0.13.0-alpha
autoinstrumentation-go=v0.14.0-alpha

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