Skip to content

Commit

Permalink
Merge branch 'main' into instrumentation-support-label
Browse files Browse the repository at this point in the history
  • Loading branch information
crossoverJie committed May 20, 2024
2 parents a4500da + ddd9f34 commit 7b754f4
Show file tree
Hide file tree
Showing 50 changed files with 1,028 additions and 1,138 deletions.
16 changes: 0 additions & 16 deletions .chloggen/2833-fix-detector-resourcedetectionprocessor.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/2862-fix-clusterrolebinding-names.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/add-collector-pool-healthy.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/cleanup-roles.yaml

This file was deleted.

17 changes: 0 additions & 17 deletions .chloggen/collector-readiness-support.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/customized-log-encoder.yaml

This file was deleted.

17 changes: 0 additions & 17 deletions .chloggen/fix-collector-node-selector.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/fix-labels-annotations-filter.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/fix-ta-check-policy.yaml

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: bug_fix
change_type: enhancement

# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
component: target allocator

# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Fix target allocator readiness check
note: Refactor allocation strategies

# One or more tracking issues related to the change
issues: [2903]
issues: [2928]

# (Optional) One or more lines of additional information to render under the primary note.
# These lines will be padded with 2 spaces and then inserted directly into the document.
# Use pipe (|) for multiline entries.
subtext:
subtext: The performance of the per-node strategy was massively improved as part of this change.

This file was deleted.

18 changes: 0 additions & 18 deletions .chloggen/ta-add-https.yaml

This file was deleted.

16 changes: 0 additions & 16 deletions .chloggen/verify-prom-crd-resources.yaml

This file was deleted.

2 changes: 1 addition & 1 deletion .github/workflows/e2e.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ jobs:
path: bin
key: ${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('Makefile') }}-${{ steps.setup-go.outputs.go-version }}
- name: Install chainsaw
uses: kyverno/action-install-chainsaw@v0.2.0
uses: kyverno/action-install-chainsaw@v0.2.1
- name: Install tools
run: make install-tools
- name: Prepare e2e tests
Expand Down
46 changes: 46 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,52 @@

<!-- next version -->

## 0.100.0

### 💡 Enhancements 💡

- `opamp`: Add healthy field at collector pool level in opamp bridge heartbeat (#2936)
- `collector`: Add support for readinessProbe on OpenTelemetryCollector CRD. (#2943)
Add support for readinessProbe on `OpenTelemetryCollector` and its default similar to the already supported livenessProbe.

- `operator`: Enabling new Logs Enconder Configuration parameters. (#268)
- `operator`: Automatically enable RBAC creation if operator SA can create clusterroles and bindings. --create-rbac-permissions flag is noop and deprecated now. (#2588)
- `target allocator`: Added option for creating an mTLS-configured HTTPS server to fetch scrape config with real secret values. (#1669)
The change introduces an option to create an additional HTTPS server with mTLS configuration.
This server is specifically utilized for obtaining the scrape configuration with actual secret values.


### 🧰 Bug fixes 🧰

- `collector`: Create a Service Monitor for the monitoring service and another one for the collector service when the Prometheus exporter is used. (#2877)
Create a Service Monitor for the collector Service when Prometheus exporter is used. A different Service Monitor is created for the monitoring service.
This helps excluding the headless service (duplicating the metrics collection) and splits responsibilities between the two Service Monitors.
Now, the operator.opentelemetry.io/collector-service-type label is used to differentiate the services.
operator.opentelemetry.io/collector-monitoring-service and operator.opentelemetry.io/collector-headless-service are deprecated now.
- `target-allocator`: Fixed non-expected warnings on TA webhook. (#2685)
- `collector`: Ensure all Prometheus CRDs are installed (#2964)
- `collector`: Cleanup ClusterRoles and ClusterRoleBindings created by the operator (#2938)
The operator uses finalizer on the collector to run the cleanup
- `collector`: Use the k8snode detector instead of kubernetes for the automatic RBAC creation for the resourcedetector (#2833)
- `collector`: When two Collectors are created with the same name but different namespaces, the ClusterRoleBinding created by the first will be overriden by the second one. (#2862)
- `collector`: Fix to reflect changes of OpenTelemetryCollector.spec.nodeSelector in the collector Pods (#2940)
When updating `OpenTelemetryCollector.spec.nodeSelector` it was not removing previous selector from the final collector pod (Deployment/Daemonset/Statefulset).

- `collector`: Fix of Labels and Annotations filter (#2770)
- `target allocator`: Fix target allocator readiness check (#2903)

### Components

* [OpenTelemetry Collector - v0.100.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.100.0)
* [OpenTelemetry Contrib - v0.100.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.100.0)
* [Java auto-instrumentation - v1.32.1](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.32.1)
* [.NET auto-instrumentation - v1.2.0](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/{AUTO_INSTRUMENTATION_DOTNET_VERSION})
* [Node.JS - v0.51.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.51.0)
* [Python - v0.44b0](https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.44b0)
* [Go - v0.12.0-alpha](https://github.com/open-telemetry/opentelemetry-go-instrumentation/releases/tag/v0.12.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.99.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 @@ -730,6 +730,7 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,

| OpenTelemetry Operator | Kubernetes | Cert-Manager |
|------------------------| -------------- | ------------ |
| v0.100.0 | v1.23 to v1.29 | v1 |
| v0.99.0 | v1.23 to v1.29 | v1 |
| v0.98.0 | v1.23 to v1.29 | v1 |
| v0.97.0 | v1.23 to v1.29 | v1 |
Expand All @@ -752,7 +753,6 @@ The OpenTelemetry Operator _might_ work on versions outside of the given range,
| v0.80.0 | v1.19 to v1.27 | v1 |
| 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 |

## Contributing and Developing

Expand Down
4 changes: 2 additions & 2 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Steps to release a new version of the OpenTelemetry Operator:

1. Create a `Prepare relese x.y.z` pull request with the following content:
1. Create a `Prepare release x.y.z` pull request with the following content:
1. Set the version you're releasing as an environment variable for convenience: `export VERSION=0.n+1.0`
1. Update `versions.txt`
- Operator, target allocator and opamp-bridge should be `$VERSION`.
Expand Down Expand Up @@ -44,9 +44,9 @@ The operator should be released within a week after the [OpenTelemetry collector

| Version | Release manager |
|----------|-----------------|
| v0.100.0 | @TylerHelmuth |
| v0.101.0 | @swiatekm-sumo |
| v0.102.0 | @frzifus |
| v0.103.0 | @jaronoff97 |
| v0.104.0 | @pavolloffay |
| v0.105.0 | @yuriolisa |
| v0.106.0 | @TylerHelmuth |
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-05-03T15:21:44Z"
createdAt: "2024-05-15T17:31:49Z"
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.99.0
name: opentelemetry-operator.v0.100.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.99.0
image: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.100.0
livenessProbe:
httpGet:
path: /healthz
Expand Down Expand Up @@ -612,7 +612,7 @@ spec:
minKubeVersion: 1.23.0
provider:
name: OpenTelemetry Community
version: 0.99.0
version: 0.100.0
webhookdefinitions:
- admissionReviewVersions:
- v1alpha1
Expand Down
Loading

0 comments on commit 7b754f4

Please sign in to comment.