Operator OPAMP Bridge

Operator OPAMP Bridge connects OpenTelemetry Collector deployments to an OPAMP server, the remote-management endpoint for OpenTelemetry agents, so you can…

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
Operator OPAMP Bridge connects OpenTelemetry Collector deployments to an OPAMP server, the remote-management endpoint for OpenTelemetry agents, so you can configure, update, and observe your telemetry pipelines from a single control point. It runs alongside the OpenTelemetry Operator on Kubernetes and suits platform teams that need to manage distributed collectors without touching each workload individually.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 17 days ago
Popular
651,775 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
1,775
Open issues
284
Last commit
2026-11-04
Latest release
v0.162.0
License
Apache-2.0
Activity
steady

Checked 17 days ago - source: GitHub (open-telemetry/opentelemetry-operator)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set VLogs disk and memory limits first Before creating VLogs, set a storage size and memory limits that match how much log data you expect. If the disk or memory is too small, VLogs can fail to start or lose logs when it runs out of room. source
  • Create the alertmanager secret first Create the Kubernetes Secret (a stored config bundle) containing alertmanager.yaml before creating VMAlertmanager, then point spec.configSecret at its name. Without that Secret, VMAlertmanager cannot load its alerting configuration and will not work properly. source
  • Istio is optional for basic use Install Istio only if you need service-mesh control over traffic between apps. It is an optional integration, and adding it during a first install can make networking harder to troubleshoot. source
  • Getting started Install on a Kubernetes cluster and follow the Getting Started guide in the repository docs to connect your collectors to your OPAMP server. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the OpenTelemetry Operator installation require cert-manager?

Yes, the docs say to make sure cert-manager is installed in the Kubernetes cluster before applying the operator manifest.

Where can I check OpAMPBridge fields while detailed docs are still planned?

Dedicated documentation for the OpAMPBridge custom resource is planned, and the API reference is available in the meantime.

Can I customize the non-identifying description for the OPAMP Bridge?

Yes, the OpAMPBridge spec includes a description field for customizing non-identifying attributes.

Can the OPAMP Bridge maintain a two-way connection with the OPAMP server?

Yes, it implements OPAMP through bidirectional communication with an OPAMP server.

Answers sourced from deepwiki.com, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads