Skip to content
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.

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

Prep 0.94.0 release #2629

Merged
merged 4 commits into from
Feb 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
18 changes: 0 additions & 18 deletions .chloggen/fix-protocol-handling-in-serviceports.yaml

This file was deleted.

18 changes: 0 additions & 18 deletions .chloggen/fix-syslog-tcplog-udplog.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/fix_2589-watch-single-namespace.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/per-node-allocation-strategy.yaml

This file was deleted.

31 changes: 31 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,37 @@ Changes by Version
==================
<!-- next version -->

## 0.94.0

### 💡 Enhancements 💡

- `target allocator`: Add new "per node" allocation strategy to target allocator. This strategy will allocate targets to nodes on which given target resides. It should only be used conjunction with the daemonset mode. (#1828)

### 🧰 Bug fixes 🧰

- `operator`: Fixed handling of protocol in exposed ports. (#2619)
Make distinction not only on the port number, but also on protocol. This fix allows to have multiple exposed
ServicePorts with the same port number, but different protocols.

- `operator`: Fixed handling of exposed port protocol in syslog, tcplog and udplog receivers. (#767, #2619)
Please note that the operator currently exposes just one port (tcp or udp) of syslog receiver due to the current
receiver implementation (patches are welcome).

- `operator`: Fixing WATCH_NAMESPACE for a single namespace value (#2589)

### Components

* [OpenTelemetry Collector - v0.94.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.94.0)
* [OpenTelemetry Contrib - v0.94.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.94.0)
* [Java auto-instrumentation - 1.32.1](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.32.1)
* [.NET auto-instrumentation - 1.2.0](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/1.2.0)
* [Node.JS - 0.46.0](https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-node-0.46.0)
* [Python - 0.43b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/0.43b0)
* [Go - v0.10.1-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.10.1-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.93.0

### 🛑 Breaking changes 🛑
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -710,6 +710,7 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,

| OpenTelemetry Operator | Kubernetes | Cert-Manager |
|------------------------|----------------------|---------------------|
| v0.94.0 | v1.23 to v1.29 | v1 |
| v0.93.0 | v1.23 to v1.29 | v1 |
| v0.92.0 | v1.23 to v1.29 | v1 |
| v0.91.0 | v1.23 to v1.29 | v1 |
Expand All @@ -732,7 +733,6 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,
| v0.74.0 | v1.19 to v1.26 | v1 |
| v0.73.0 | v1.19 to v1.26 | v1 |
| v0.72.0 | v1.19 to v1.26 | v1 |
| v0.71.0 | v1.19 to v1.25 | v1 |

## Contributing and Developing

Expand Down
2 changes: 1 addition & 1 deletion RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,10 @@ The operator should be released within a week after the [OpenTelemetry collector

| Version | Release manager |
|----------|-----------------|
| v0.94.0 | @TylerHelmuth |
| v0.95.0 | @swiatekm-sumo |
| v0.96.0 | @frzifus |
| v0.97.0 | @jaronoff97 |
| v0.98.0 | @yuriolisa |
| v0.99.0 | @pavolloffay |
| v0.100.0 | @VineethReddy02 |
| v0.101.0 | @TylerHelmuth |
Copy link
Member

Choose a reason for hiding this comment

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

🔨

2 changes: 1 addition & 1 deletion bundle.Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,4 @@ LABEL operators.operatorframework.io.test.config.v1=tests/scorecard/
COPY bundle/manifests /manifests/
COPY bundle/metadata /metadata/
COPY bundle/tests/scorecard /tests/scorecard/
LABEL com.redhat.openshift.versions="v4.11-v4.15"
LABEL com.redhat.openshift.versions="v4.12-v4.15"
Original file line number Diff line number Diff line change
Expand Up @@ -65,13 +65,13 @@ metadata:
categories: Logging & Tracing,Monitoring
certified: "false"
containerImage: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
createdAt: "2024-02-02T16:02:46Z"
createdAt: "2024-02-15T18:18:46Z"
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.93.0
name: opentelemetry-operator.v0.94.0
namespace: placeholder
spec:
apiservicedefinitions: {}
Expand Down Expand Up @@ -402,7 +402,7 @@ spec:
- --zap-log-level=info
- --zap-time-encoding=rfc3339nano
- --feature-gates=+operator.autoinstrumentation.go,+operator.autoinstrumentation.nginx
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.93.0
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.94.0
livenessProbe:
httpGet:
path: /healthz
Expand Down Expand Up @@ -510,7 +510,7 @@ spec:
minKubeVersion: 1.23.0
provider:
name: OpenTelemetry Community
version: 0.93.0
version: 0.94.0
webhookdefinitions:
- admissionReviewVersions:
- v1
Expand Down
2 changes: 1 addition & 1 deletion bundle/metadata/annotations.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,4 @@ annotations:
operators.operatorframework.io.test.config.v1: tests/scorecard/

# OpenShift specific annotations
com.redhat.openshift.versions: "v4.11-v4.15"
com.redhat.openshift.versions: "v4.12-v4.15"
2 changes: 1 addition & 1 deletion hack/add-openshift-annotations.sh
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
#!/bin/bash

OPENSHIFT_VERSIONS="\"v4.11-v4.15\""
OPENSHIFT_VERSIONS="\"v4.12-v4.15\""

{
echo ""
Expand Down
10 changes: 5 additions & 5 deletions versions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,20 @@
# 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.93.0
opentelemetry-collector=0.94.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

The libraries are, but not the released images: https://github.com/open-telemetry/opentelemetry-collector-releases/releases


# Represents the current release of the OpenTelemetry Operator.
operator=0.93.0
operator=0.94.0

# Represents the current release of the Target Allocator.
targetallocator=0.93.0
targetallocator=0.94.0

# Represents the current release of the Operator OpAMP Bridge.
operator-opamp-bridge=0.93.0
operator-opamp-bridge=0.94.0

# Represents the current release of Java instrumentation.
# Should match autoinstrumentation/java/version.txt
autoinstrumentation-java=1.32.0
autoinstrumentation-java=1.32.1

# Represents the current release of NodeJS instrumentation.
# Should match value in autoinstrumentation/nodejs/package.json
Expand Down
Loading