opentelemetry-collector
OpenTelemetry-Collector Overview
Secure your stack with a hardened OpenTelemetry Collector image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.
The OpenTelemetry Collector is used to collect, process, and export telemetry data (logs, metrics, traces) from applications and infrastructure with support for many backends and integrations. It includes a wide range of receivers, processors, exporters, and extensions.
Try It Out
Prerequisites
- A running Kubernetes cluster (v1.21 or higher is recommended)
- Helm v3.8 or higher for OCI support (Installation instructions)
kubectlinstalled and configured
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Add Repository to your Local Client
Add the Helm chart to your local Helm client.
helm repo add opentelemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm repo updateStep 3: Deploy via Helm Chart
Deploy the Pod in the daemonset mode as an agent (one collector per node):
helm install opentelemetry-collector opentelemetry/opentelemetry-collector \
--namespace telemetry-ns \
--create-namespace \
--set mode=daemonset \
--set image.repository=reg.mini.dev/opentelemetry-collector \
--set image.tag=latestConfirm that the Minimus image was deployed:
kubectl -n telemetry-ns describe pods | grep Image:Check the Pod:
kubectl get po -n telemetry-nsStep 4: Clean Up
Uninstall the chart to delete the namespace and its resources, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:
helm uninstall opentelemetry-collector -n telemetry-nsTechnical Considerations
The OpenTelemetry-Collector image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.
OpenTelemetry-Collector built by Minimus:
- Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
- Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.
The Payoff
A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.
- See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
- Review the compliance report to see the default hardening and security configurations for the image.
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.