You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`OpAMP Bridge`: Currently, the bridge doesn't adhere to the spec for the naming structure. This changes the bridge to use the <namespace>/<otelcol> structure as described. (#2131)
10
53
* Updates the bridge to get collectors using the reporting annotation
11
54
* Fixes a bug where we were using the incorrect structure for the collectors
12
-
55
+
13
56
14
57
### 💡 Enhancements 💡
15
58
@@ -45,7 +88,7 @@ Changes by Version
45
88
-`operator`: Enable Target Allocator Rewrite by default (#2208)
46
89
See [the documentation](/README.md#target-allocator) for details.
47
90
Use the `--feature-gates=-operator.collector.rewritetargetallocator` command line option to switch back to the old behaviour.
48
-
91
+
49
92
50
93
### 💡 Enhancements 💡
51
94
@@ -78,7 +121,7 @@ Changes by Version
78
121
Kubernetes 1.23 is the minimum available version everywhere after 1.22 deprecation,
79
122
due to it, the minimum required version has been updated to it, dropping support for
80
123
autoscaling/v2beta2
81
-
124
+
82
125
83
126
### 💡 Enhancements 💡
84
127
@@ -171,12 +214,12 @@ Changes by Version
171
214
### 🛑 Breaking changes 🛑
172
215
173
216
-`operator`: Make sure OTLP export can report data to OTLP ingress/route without additional configuration (#1967)
174
-
The ingress can be configured to create a single host with multiple paths or
217
+
The ingress can be configured to create a single host with multiple paths or
175
218
multiple hosts with subdomains (one per receiver port).
176
219
The path from OpenShift route was removed.
177
220
The port names are truncate to 15 characters. Users with custom receivers
178
221
which create ports with longer name might need to update their configuration.
Copy file name to clipboardexpand all lines: README.md
+9-5
Original file line number
Diff line number
Diff line change
@@ -223,6 +223,13 @@ spec:
223
223
# See https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/888e2cd216c77d12e56b54ee91dafbc4e7452a52/docs/config.md#otlp
224
224
- name: OTEL_EXPORTER_OTLP_ENDPOINT
225
225
value: http://otel-collector:4318
226
+
go:
227
+
env:
228
+
# Required if endpoint is set to 4317.
229
+
# Go autoinstrumentation uses http/proto by default
230
+
# so data must be sent to 4318 instead of 4317.
231
+
- name: OTEL_EXPORTER_OTLP_ENDPOINT
232
+
value: http://otel-collector:4318
226
233
EOF
227
234
```
228
235
@@ -279,9 +286,6 @@ Go auto-instrumentation also requires elevated permissions. The below permission
279
286
280
287
```yaml
281
288
securityContext:
282
-
capabilities:
283
-
add:
284
-
- SYS_PTRACE
285
289
privileged: true
286
290
runAsUser: 0
287
291
```
@@ -534,7 +538,7 @@ OpenTelemetry Operator allows to instrument multiple containers using multiple l
534
538
These features can be enabled using `operator.autoinstrumentation.multi-instrumentation` flag when installing the Operator via Helm. By default flag is `disabled`. For example:
For more information about multi-instrumentation feature capabilities please see [Multi-container pods with multiple instrumentations](#Multi-container-pods-with-multiple-instrumentations).
@@ -682,6 +686,7 @@ The OpenTelemetry Operator *might* work on versions outside of the given range,
0 commit comments