
Service Provider: OTEL Operator
An OpenMCP Service Provider that automates the deployment and lifecycle management of the OpenTelemetry Operator into Managed Control Planes (MCPs) via Helm.
Overview
This service provider installs the OpenTelemetry Operator into each MCP that requests one. The operator is deployed using the official opentelemetry-operator Helm chart. Once the operator is running, users can create OpenTelemetryCollector custom resources in the MCP to configure and manage collector instances.
Architecture
Platform Cluster MCP (per tenant)
┌─────────────────────┐ ┌──────────────────────────────────────────┐
│ ProviderConfig │ │ namespace: opentelemetry-operator-system│
│ (cluster-scoped) │ │ │
│ - chartVersion │ │ Helm Release: opentelemetry-operator │ ← SP creates
│ - chartRepoURL │ │ → Deployment (operator) │
│ - helmValues │ │ → CRDs (OpenTelemetryCollector, etc.) │
│ - imagePullSecrets │ │ → RBAC, Webhooks, Services │
└─────────────────────┘ │ │
│ OpenTelemetryCollector CRs │ ← user creates
Onboarding Cluster └──────────────────────────────────────────┘
┌──────────────────────┐
│ OtelOperator │ ← one per MCP
│ (per-MCP overrides) │
└──────────────────────┘
Reconciliation Flow
- Set status to
Progressing
- Ensure the target namespace exists in the MCP
- Sync image pull secrets from the platform cluster to the MCP (if configured)
- Merge Helm values (ProviderConfig defaults + per-MCP overrides)
- Install or upgrade the
opentelemetry-operator Helm release
- Set status to
Ready
On deletion, the service provider uninstalls the Helm release, which removes all operator-managed resources from the MCP.
cert-manager
The OpenTelemetry Operator Helm chart supports cert-manager for webhook certificate management. By default, this service provider disables cert-manager and uses auto-generated self-signed certificates instead (admissionWebhooks.autoGenerateCert.enabled: true). This makes the operator self-contained without requiring cert-manager in the MCP.
If cert-manager is available in your MCPs, you can enable it via the ProviderConfig's helmValues:
spec:
helmValues:
admissionWebhooks:
certManager:
enabled: true
autoGenerateCert:
enabled: false
API
OtelOperator (onboarding cluster)
Created per MCP to request an OpenTelemetry Operator installation. All fields are optional overrides — defaults come from the ProviderConfig.
apiVersion: oteloperator.services.openmcp.cloud/v1alpha1
kind: OtelOperator
metadata:
name: my-mcp
spec:
# All fields are optional — defaults from ProviderConfig are used if omitted
chartVersion: "0.82.0"
namespace: "opentelemetry-operator-system"
helmValues:
manager:
collectorImage:
repository: "otel/opentelemetry-collector-contrib"
Cluster-scoped resource that provides default values for all MCPs.
apiVersion: oteloperator.services.openmcp.cloud/v1alpha1
kind: ProviderConfig
metadata:
name: oteloperator
spec:
pollInterval: 1m
chartVersion: "0.82.0"
chartRepoURL: "https://open-telemetry.github.io/opentelemetry-helm-charts"
defaultNamespace: "opentelemetry-operator-system"
imagePullSecrets:
- name: my-registry-secret
helmValues:
admissionWebhooks:
certManager:
enabled: false
autoGenerateCert:
enabled: true
Project Structure
├── api/
│ ├── v1alpha1/ # API types (OtelOperator, ProviderConfig)
│ └── crds/ # Embedded CRD manifests
├── cmd/
│ └── service-provider-otel-operator/ # Entrypoint (init + run commands)
├── internal/
│ ├── controller/ # Reconciler (CreateOrUpdate / Delete)
│ ├── helm/ # Helm SDK integration (install/upgrade/uninstall)
│ └── resources/ # Kubernetes resource helpers
│ ├── constants.go # Labels
│ ├── namespace.go # Namespace reconciliation
│ └── imagepullsecret.go # Image pull secret sync (platform → MCP)
├── pkg/
│ └── spruntime/ # Generic SP/PC reconciler framework
├── test/
│ └── e2e/ # End-to-end tests
└── hack/ # Build tooling
Development
Prerequisites
- Go 1.25+
- Task (build system)
- Docker (for building images and running e2e tests)
- Access to an OpenMCP environment (for e2e tests)
- On macOS: GNU
realpath is required for e2e tests (brew install coreutils)
Build
go build ./...
Docker
# Build image for current platform (used by e2e tests)
task build:img:build-test
Run Tests
# Unit tests
task test
# End-to-end tests (requires Docker for kind clusters)
task test-e2e
Generate CRDs and DeepCopy
task generate
task validate
CLI Flags
The service provider binary accepts a command (init or run) as its first argument, followed by flags:
| Flag |
Default |
Description |
--environment |
"" |
Name of the environment |
--provider-name |
"" |
Name of the provider resource |
--metrics-bind-address |
0 |
Address for the metrics endpoint (:8443 for HTTPS, :8080 for HTTP, 0 to disable) |
--health-probe-bind-address |
:8081 |
Address for health probe endpoint |
--leader-elect |
false |
Enable leader election |
--metrics-secure |
true |
Serve metrics via HTTPS |
--enable-http2 |
false |
Enable HTTP/2 for metrics and webhook servers |
--verbosity |
|
Logging verbosity level |
Support, Feedback, Contributing
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
Security / Disclosure
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
Code of Conduct
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Licensing
Copyright 2025 SAP SE or an SAP affiliate company and service-provider-otel-operator contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.