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
Copy file name to clipboardexpand all lines: .chloggen/3267-custom-instr-vol.yaml
+4-6
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,15 @@
2
2
change_type: enhancement
3
3
4
4
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
5
-
component: target allocator, collector
5
+
component: auto-instrumentation
6
6
7
7
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
-
note: "Enable mTLS between the TA and collector for passing secrets in the scrape_config securely"
8
+
note: Adds VolumeClaimTemplate field to Instrumentation spec to enable user-definable ephemeral volumes for auto-instrumentation.
9
9
10
10
# One or more tracking issues related to the change
11
-
issues: [1669]
11
+
issues: [3267]
12
12
13
13
# (Optional) One or more lines of additional information to render under the primary note.
14
14
# These lines will be padded with 2 spaces and then inserted directly into the document.
15
15
# Use pipe (|) for multiline entries.
16
-
subtext: |
17
-
This change enables mTLS between the collector and the target allocator (requires cert-manager).
18
-
This is necessary for passing secrets securely from the TA to the collector for scraping endpoints that have authentication.
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
2
+
change_type: enhancement
3
+
4
+
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
5
+
component: collector
6
+
7
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
+
note: "Add support for persistentVolumeClaimRetentionPolicy field"
9
+
10
+
# One or more tracking issues related to the change
11
+
issues: [3305]
12
+
13
+
# (Optional) One or more lines of additional information to render under the primary note.
14
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
2
+
change_type: enhancement
3
+
4
+
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
5
+
component: auto-instrumentation
6
+
7
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
+
note: Add Nodejs auto-instrumentation image builds for linux/s390x,linux/ppc64le.
9
+
10
+
# One or more tracking issues related to the change
11
+
issues: [3322]
12
+
13
+
# (Optional) One or more lines of additional information to render under the primary note.
14
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
Copy file name to clipboardexpand all lines: .chloggen/ta-no-root.yaml
+4-6
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,15 @@
2
2
change_type: bug_fix
3
3
4
4
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
5
-
component: collector-webhook
5
+
component: target allocator
6
6
7
7
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
-
note: "Fixed validation of `stabilizationWindowSeconds` in autoscaler behaviour"
8
+
note: Change docker image to run as non-root
9
9
10
10
# One or more tracking issues related to the change
11
-
issues: [3345]
11
+
issues: [3378]
12
12
13
13
# (Optional) One or more lines of additional information to render under the primary note.
14
14
# These lines will be padded with 2 spaces and then inserted directly into the document.
15
15
# Use pipe (|) for multiline entries.
16
-
subtext: |
17
-
The validation of `stabilizationWindowSeconds` in the `autoscaler.behaviour.scale[Up|Down]` incorrectly rejected 0 as an invalid value.
18
-
This has been fixed to ensure that the value is validated correctly (should be >=0 and <=3600) and the error messsage has been updated to reflect this.
Copy file name to clipboardexpand all lines: CHANGELOG.md
+67
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,73 @@
2
2
3
3
<!-- next version -->
4
4
5
+
## 0.111.0
6
+
7
+
### 💡 Enhancements 💡
8
+
9
+
-`auto-instrumentation`: set OTEL_LOGS_EXPORTER env var to otlp in python instrumentation (#3330)
10
+
11
+
-`collector`: Expose the Collector telemetry endpoint by default. (#3361)
12
+
13
+
The collector v0.111.0 changes the default binding of the telemetry metrics endpoint from `0.0.0.0` to `localhost`.
14
+
To avoid any disruption we fallback to `0.0.0.0:{PORT}` as default address.
15
+
Details can be found here: [opentelemetry-collector#11251](https://github.com/open-telemetry/opentelemetry-collector/pull/11251)
16
+
17
+
18
+
-`auto-instrumentation`: Add support for specifying exporter TLS certificates in auto-instrumentation. (#3338)
19
+
20
+
Now Instrumentation CR supports specifying TLS certificates for exporter:
21
+
```yaml
22
+
spec:
23
+
exporter:
24
+
endpoint: https://otel-collector:4317
25
+
tls:
26
+
secretName: otel-tls-certs
27
+
configMapName: otel-ca-bundle
28
+
# otel-ca-bundle
29
+
ca_file: ca.crt
30
+
# present in otel-tls-certs
31
+
cert_file: tls.crt
32
+
# present in otel-tls-certs
33
+
key_file: tls.key
34
+
```
35
+
36
+
* Propagating secrets across namespaces can be done with https://github.com/EmberStack/kubernetes-reflector or https://github.com/zakkg3/ClusterSecret
37
+
* Restarting workloads on certificate renewal can be done with https://github.com/stakater/Reloader or https://github.com/wave-k8s/wave
38
+
39
+
- `collector`: Add native sidecar injection behind a feature gate which is disabled by default. (#2376)
40
+
41
+
Native sidecars are supported since Kubernetes version `1.28` and are availabe by default since `1.29`.
42
+
To use native sidecars on Kubernetes v1.28 make sure the "SidecarContainers" feature gate on kubernetes is enabled.
43
+
If native sidecars are available, the operator can be advised to use them by adding
44
+
the `--feature-gates=operator.sidecarcontainers.native` to the Operator args.
45
+
In the future this may will become availabe as deployment mode on the Collector CR. See [#3356](https://github.com/open-telemetry/opentelemetry-operator/issues/3356)
46
+
47
+
- `target allocator, collector`: Enable mTLS between the TA and collector for passing secrets in the scrape_config securely (#1669)
48
+
49
+
This change enables mTLS between the collector and the target allocator (requires cert-manager).
50
+
This is necessary for passing secrets securely from the TA to the collector for scraping endpoints that have authentication. Use the `operator.targetallocator.mtls` to enable this feature. See the target allocator [documentation](https://github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator#service--pod-monitor-endpoint-credentials) for more details.
51
+
52
+
### 🧰 Bug fixes 🧰
53
+
54
+
- `collector-webhook`: Fixed validation of `stabilizationWindowSeconds` in autoscaler behaviour (#3345)
55
+
56
+
The validation of `stabilizationWindowSeconds` in the `autoscaler.behaviour.scale[Up|Down]` incorrectly rejected 0 as an invalid value.
57
+
This has been fixed to ensure that the value is validated correctly (should be >=0 and <=3600) and the error messsage has been updated to reflect this.
Copy file name to clipboardexpand all lines: README.md
+7-15
Original file line number
Diff line number
Diff line change
@@ -608,7 +608,7 @@ spec:
608
608
mode: statefulset
609
609
targetAllocator:
610
610
enabled: true
611
-
config:
611
+
config:
612
612
receivers:
613
613
prometheus:
614
614
config:
@@ -740,7 +740,7 @@ spec:
740
740
741
741
### Configure resource attributes with labels
742
742
743
-
You can also use common labels to set resource attributes.
743
+
You can also use common labels to set resource attributes.
744
744
745
745
The following labels are supported:
746
746
- `app.kubernetes.io/name`becomes `service.name`
@@ -782,12 +782,12 @@ The priority for setting resource attributes is as follows (first found wins):
782
782
783
783
1. Resource attributes set via `OTEL_RESOURCE_ATTRIBUTES` and `OTEL_SERVICE_NAME` environment variables
784
784
2. Resource attributes set via annotations (with the `resource.opentelemetry.io/` prefix)
785
-
3. Resource attributes set via labels (e.g. `app.kubernetes.io/name`)
785
+
3. Resource attributes set via labels (e.g. `app.kubernetes.io/name`)
786
786
if the `Instrumentation` CR has defaults.useLabelsForResourceAttributes=true (see above)
787
787
4. Resource attributes calculated from the pod's metadata (e.g. `k8s.pod.name`)
788
788
5. Resource attributes set via the `Instrumentation` CR (in the `spec.resource.resourceAttributes` section)
789
789
790
-
This priority is applied for each resource attribute separately, so it is possible to set some attributes via
790
+
This priority is applied for each resource attribute separately, so it is possible to set some attributes via
791
791
annotations and others via labels.
792
792
793
793
## Compatibility matrix
@@ -807,12 +807,13 @@ We strive to be compatible with the widest range of Kubernetes versions as possi
807
807
We use `cert-manager` for some features of this operator and the third column shows the versions of the `cert-manager` that are known to work with this operator's versions.
808
808
809
809
The Target Allocator supports prometheus-operator CRDs like ServiceMonitor, and it does so by using packages imported from prometheus-operator itself. The table shows which version is shipped with a given operator version.
810
-
Generally speaking, these are backwards compatible, but specific features require the appropriate package versions.
810
+
Generally speaking, these are backwards compatible, but specific features require the appropriate package versions.
811
811
812
812
The OpenTelemetry Operator _might_ work on versions outside of the given range, but when opening new issues, please make sure to test your scenario on a supported version.
0 commit comments