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
Introduces a new standalone mode that allows managing collector config from a remote server without requiring Operator CRDs.
Adds the standalone client, a plain collector instance type, Kubernetes RBAC and deployment manifests, and a --mode flag to select between operator (default) and standalone at startup.
# 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: opamp-bridge
6
+
7
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
+
note: OpAMP Bridge standalone mode
9
+
10
+
# One or more tracking issues related to the change
11
+
issues: [4913]
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.
15
+
# Use pipe (|) for multiline entries.
16
+
subtext: |
17
+
Standalone mode for OpAMP Bridge allows users to manage collector configuration from a remote
18
+
OpAMP server without the need to deploy full Otel Operator.
Copy file name to clipboardExpand all lines: cmd/operator-opamp-bridge/README.md
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,55 @@ There are two main ways to install the OpAMP Bridge:
20
20
21
21
## Usage
22
22
23
+
### Standalone mode
24
+
25
+
Standalone mode lets the bridge manage Collector configuration stored in Kubernetes `ConfigMap` resources, without creating `OpenTelemetryCollector` CRDs. This is useful when the Collector workload is managed outside the operator, but the config still needs to be reported to and updated from an OpAMP server.
26
+
27
+
Start the bridge with `mode: standalone` in its config file, or pass `--mode=standalone`:
28
+
29
+
```yaml
30
+
endpoint: "<OPAMP_SERVER_ENDPOINT>"
31
+
mode: standalone
32
+
capabilities:
33
+
AcceptsRemoteConfig: true
34
+
ReportsEffectiveConfig: true
35
+
ReportsRemoteConfig: true
36
+
```
37
+
38
+
In this mode, the bridge watches ConfigMaps labeled with `opentelemetry.io/managed-by: opamp-bridge-standalone`. Each managed ConfigMap is reported to the OpAMP server as `kind/namespace/name`, for example `configmap/default/collector-config`.
The bridge will create a missing ConfigMap, but it will only update an existing ConfigMap if that managed-by label is present. Remote deletion is not supported in standalone mode.
69
+
70
+
Standalone mode needs RBAC for ConfigMaps and for any workload kinds used as rollout targets. The repository includes a starter manifest at [`config/standalone-bridge/rbac.yaml`](../../config/standalone-bridge/rbac.yaml).
71
+
23
72
### OpAMPBridge CRD
24
73
25
74
The [OpAMPBridge](../../docs/api/opampbridges.md) CRD is used to create an OpAMP Bridge instance.
0 commit comments