Skip to content

Commit

Permalink
Prepare for 0.66.0 release (#1284)
Browse files Browse the repository at this point in the history
* Prepare for 0.66.0 release
  • Loading branch information
VineethReddy02 authored Nov 30, 2022
1 parent 1d90292 commit 7f0efd6
Show file tree
Hide file tree
Showing 5 changed files with 34 additions and 16 deletions.
17 changes: 17 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,22 @@
Changes by Version
==================
0.66.0
------------------
### 🚀 New components 🚀
* Add ingressClassName field to collector spec ([#1269](https://github.com/open-telemetry/opentelemetry-operator/pull/1269), [@avadhut123pisal](https://github.com/avadhut123pisal))
* Add secure ciphersuites for TLS config ([#1244](https://github.com/open-telemetry/opentelemetry-operator/pull/1244), [@kangsheng89](https://github.com/kangsheng89))
* Add Apache-httpd instrumentation v1.0 (part-1) ([#1236](https://github.com/open-telemetry/opentelemetry-operator/pull/1236), [@chrlic](https://github.com/chrlic))
### 💡 Enhancements 💡
* Update the javaagent version to 1.20.2 ([#1212](https://github.com/open-telemetry/opentelemetry-operator/pull/1270))
* Bump OTel .NET AutoInstrumentation to 0.5.0 ([#1276](https://github.com/open-telemetry/opentelemetry-operator/pull/1276), [@pellared](https://github.com/pellared))

### 🧰 Bug fixes 🧰
* Fix bug found when using relabel-config filterStrategy with serviceMonitors ([#1232](https://github.com/open-telemetry/opentelemetry-operator/pull/1232), [@moh-osman3](https://github.com/moh-osman3))

#### OpenTelemetry Collector and Contrib
* [OpenTelemetry Collector - v0.66.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.66.0)
* [OpenTelemetry Contrib - v0.66.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.66.0)

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

| OpenTelemetry Operator | Kubernetes | Cert-Manager |
|------------------------|----------------------|----------------------|
| v0.66.0 | v1.19 to v1.25 | v1 |
| v0.64.1 | v1.19 to v1.25 | v1 |
| v0.63.1 | v1.19 to v1.25 | v1 |
| v0.62.1 | v1.19 to v1.25 | v1 |
Expand All @@ -347,7 +348,6 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,
| v0.47.0 | v1.19 to v1.23 | v1alpha2 |
| v0.46.0 | v1.19 to v1.23 | v1alpha2 |
| v0.45.0 | v1.21 to v1.23 | v1alpha2 |
| v0.44.0 | v1.21 to v1.23 | v1alpha2 |



Expand Down
15 changes: 8 additions & 7 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,14 @@
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.
1. Run `make bundle USER=open-telemetry VERSION=0.38.0`, using the version that will be released.
1. 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, with N-2 being the lower bound. Make sure that the CI is currently testing the latest Kubernetes version!
1. Add the changes to the changelog
1. Check the OpenTelemetry Collector's changelog and ensure migration steps are present in `pkg/collector/upgrade`
1. Once the changes above are merged and available in `main`, tag it with the desired version, prefixed with `v`: `v0.38.0`
1. The GitHub Workflow will take it from here, creating a GitHub release with the generated artifacts (manifests) and publishing the images
1. After the release, generate a new OLM bundle (`make bundle`) and create two PRs against the `Community Operators repositories`:
2. Change the `autoinstrumentation-*` versions in `versions.txt` as per the latest supported versions in `auto-instrumentation/`.
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, with N-2 being the lower bound. Make sure that the CI is currently testing the latest Kubernetes version!
5. Add the changes to the changelog
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`
8. The GitHub Workflow will take it from here, creating a GitHub release with the generated artifacts (manifests) and publishing the images
9. After the release, generate a new OLM bundle (`make bundle`) and create two PRs against the `Community Operators repositories`:
1. one for the `community-operators-prod`, used by OLM on Kubernetes. Example: [`operator-framework/community-operators-prod`](https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/494)
1. one for the `community-operators` directory, used by Operatorhub.io. Example: [`operator-framework/community-operators`](https://github.com/k8s-operatorhub/community-operators/pull/461)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,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.64.1
name: opentelemetry-operator.v0.66.0
namespace: placeholder
spec:
apiservicedefinitions: {}
Expand Down Expand Up @@ -294,7 +294,7 @@ spec:
- --enable-leader-election
- --zap-log-level=info
- --zap-time-encoding=rfc3339nano
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.64.1
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.66.0
livenessProbe:
httpGet:
path: /healthz
Expand Down Expand Up @@ -401,7 +401,7 @@ spec:
maturity: alpha
provider:
name: OpenTelemetry Community
version: 0.64.1
version: 0.66.0
webhookdefinitions:
- admissionReviewVersions:
- v1
Expand Down
10 changes: 5 additions & 5 deletions versions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -2,25 +2,25 @@
# 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.64.1
opentelemetry-collector=0.66.0

# Represents the current release of the OpenTelemetry Operator.
operator=0.64.1
operator=0.66.0

# Represents the current release of the Target Allocator.
targetallocator=0.64.1
targetallocator=0.66.0

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

# Represents the current release of NodeJS instrumentation.
# Should match value in autoinstrumentation/nodejs/package.json
autoinstrumentation-nodejs=0.31.0

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

# Represents the current release of DotNet instrumentation.
# Should match autoinstrumentation/dotnet/version.txt
Expand Down

0 comments on commit 7f0efd6

Please sign in to comment.