1# Default values for opentelemetry-collector.
2# This is a YAML-formatted file.
3# Declare variables to be passed into your templates.
7# Valid values are "daemonset", "deployment", and "statefulset".
9# Override the default apiVersion for custom controllers or for testing new API versions.
11# Specify which namespace should be used to deploy the resources into
13# Handles basic configuration of components that
14# also require k8s modifications to work correctly.
15# .Values.config can be used to modify/add to a preset
16# component configuration, but CANNOT be used to remove
17# preset configuration. If you require removal of any
18# sections of a preset configuration, you cannot use
19# the preset. Instead, configure the component manually in
20# .Values.config and use the other fields supplied in the
21# values.yaml to configure k8s as necessary.
23 # Configures the collector to collect logs.
24 # Adds the file_log receiver to the logs pipeline
25 # and adds the necessary volumes and volume mounts.
26 # Best used with mode = daemonset.
27 # See https://opentelemetry.io/docs/kubernetes/collector/components/#filelog-receiver for details on the receiver.
30 includeCollectorLogs: false
31 # Enabling this writes checkpoints in /var/lib/otelcol/ host directory.
32 # Note this changes collector's user to root, so that it can write to host directory.
33 storeCheckpoints: false
34 # The maximum bytes size of the recombined field.
35 # Once the size exceeds the limit, all received entries of the source will be combined and flushed.
36 maxRecombineLogSize: 102400
37 # Configures the collector to collect host metrics.
38 # Adds the hostmetrics receiver to the metrics pipeline
39 # and adds the necessary volumes and volume mounts.
40 # Best used with mode = daemonset.
41 # See https://opentelemetry.io/docs/kubernetes/collector/components/#host-metrics-receiver for details on the receiver.
44 # Configures the Kubernetes Processor to add Kubernetes metadata.
45 # Adds the k8s_attributes processor to all the pipelines
46 # and adds a preset of minimum required RBAC rules to ClusterRole.
47 # Best used with mode = daemonset.
48 # See https://opentelemetry.io/docs/kubernetes/collector/components/#kubernetes-attributes-processor for details on the receiver.
51 # When enabled the processor will extract all labels for an associated pod and add them as resource attributes.
52 # The label's exact name will be the key.
53 extractAllPodLabels: false
54 # When enabled the processor will extract all annotations for an associated pod and add them as resource attributes.
55 # The annotation's exact name will be the key.
56 extractAllPodAnnotations: false
57 # Configures the collector to collect node, pod, and container metrics from the API server on a kubelet.
58 # Adds the kubeletstats receiver to the metrics pipeline
59 # and adds the necessary rules to ClusterRole.
60 # Best used with mode = daemonset.
61 # See https://opentelemetry.io/docs/kubernetes/collector/components/#kubeletstats-receiver for details on the receiver.
64 # Configures the collector to collect kubernetes events.
65 # Adds the k8sobjects receiver to the logs pipeline
66 # and collects kubernetes events by default.
67 # Best used with mode = deployment or statefulset.
68 # See https://opentelemetry.io/docs/kubernetes/collector/components/#kubernetes-objects-receiver for details on the receiver.
71 # When enabled, the preset uses the k8s_events receiver instead of k8sobjects. Will default to true in a future release.
72 useK8sEventsReceiver: false
73 # Collects Kubernetes objects via the k8sobjects receiver in pull mode (default interval: 1h).
74 # Can be used with mode = deployment, statefulset, or daemonset.
75 # Compatible with kubernetesEvents preset. Extra resources can be added via
76 # config.receivers.k8sobjects.objects (ClusterRole rules must be added manually via clusterRole.rules).
79 # When enabled with mode = daemonset, leader election is setup to prevent telemetry duplication.
80 # disableLeaderElection: false
81 # When enabled, watch mode is added alongside pull to stream real-time changes.
83 # Core Kubernetes workload resources: pods, nodes, namespaces, services, serviceaccounts, deployments, replicasets, daemonsets, statefulsets, jobs, cronjobs
86 # RBAC resources: roles, rolebindings, clusterroles, clusterrolebindings
89 # Storage resources: storageclasses, persistentvolumes, persistentvolumeclaims
92 # Networking resources: ingresses, networkpolicies
95 # Autoscaling resources: horizontalpodautoscalers
98 # VPA resources: verticalpodautoscalers (requires VPA CRD to be installed)
101 # Policy resources: poddisruptionbudgets
104 # API extensions resources: customresourcedefinitions
107 # Kubernetes events, collected in watch mode.
110 # Configures the Kubernetes Cluster Receiver to collect cluster-level metrics.
111 # Adds the k8s_cluster receiver to the metrics pipeline
112 # and adds the necessary rules to ClusterRole.
113 # Can be used with mode = deployment, statefulset, or daemonset.
114 # When used as a daemonset or with multiple replicas, leader election is set up to prevent duplication.
115 # See https://opentelemetry.io/docs/kubernetes/collector/components/#kubernetes-cluster-receiver for details on the receiver.
118 # When enabled with mode = daemonset or with multiple replicas, leader election is set up to prevent telemetry duplication.
119 # disableLeaderElection: false
120 # Configures the collector to collect logs and metrics from pods with specific annotations.
121 # This preset can not be used together with the `logsCollection` preset.
122 # Adds the receiver_creator receiver to the logs and metrics pipelines
123 # and adds the necessary rules to ClusterRole.
124 # Best used with mode = daemonset.
125 # See https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/receivercreator/README.md#generate-receiver-configurations-from-provided-hints for details on the receiver.
131 # Configures the collector to collect profiling data.
132 # Adds profiles pipeline with the profiling receiver,
133 # and adds the necessary volumes, security context and host PID access.
135 # Warning: The profiling receiver requires elevated capabilities and hostPID,
136 # so it should be used with a dedicated collector distribution (e.g. otelcol-ebpf-profiler)
137 # rather than the general-purpose k8s distribution. This avoids granting elevated privileges
138 # to the same collector that handles metrics, traces, and logs.
139 # See https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-ebpf-profiler for more details.
140 # When enabled, the collector is also scheduled on Linux nodes only.
143 # Configures the collector to detect resource attributes using the resourcedetection processor.
144 # Adds the resourcedetection/env processor to all pipelines.
145 # Each detector can be enabled individually. Base detectors 'env' and 'k8s_api' are always included when any detector is enabled.
146 # Typically used to resolve the 'k8s.cluster.name' resource attribute.
147 # See https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor for details.
161 # Specifies whether a configMap should be created (true by default)
163 # Specifies an existing ConfigMap to be mounted to the pod
164 # The ConfigMap MUST include the collector configuration via a key named 'relay' or the collector will not start.
165 # This also supports template content, which will eventually be converted to yaml.
167 # Specifies the relative path to custom ConfigMap template file. This option SHOULD be used when bundling a custom
168 # ConfigMap template, as it enables pod restart via a template checksum annotation.
170# When enabled, the chart will configure the collector to emit its traces, metrics, and logs over http via the OTLP using the Otel Go SDK.
171# If internalTelemetryViaOTLP.metrics.enabled the chart will remove the default prometheus receiver (which was configured to scrape the Collector's metrics).
172# Learn more about the Collector telemetry at https://opentelemetry.io/docs/collector/internal-telemetry/.
174# THIS OPTION IS EXPERIMENTAL AND SUBJECT TO BREAKING CHANGES
175internalTelemetryViaOTLP:
176 # The endpoint where the telemetry will be exported
178 # Optional headers to configure the exporters
180 # - name: "x-dest-auth"
181 # value: "some auth key"
184 # overrides internalTelemetryViaOTLP.endpoint for traces
186 # overrides internalTelemetryViaOTLP.headers for traces
190 # overrides internalTelemetryViaOTLP.endpoint for metrics
192 # overrides internalTelemetryViaOTLP.headers for metrics
196 # overrides internalTelemetryViaOTLP.endpoint for logs
198 # overrides internalTelemetryViaOTLP.headers for logs
200# Rewrite deprecated component names (e.g. k8sattributes -> k8s_attributes
201# processor, k8snode -> k8s_api resourcedetection detector) in the generated
202# config. Set to false if using older Collector images that do not recognize the
203# new names. Renamed from rewriteDeprecatedProcessorNames in chart 0.162.0.
204rewriteDeprecatedComponentNames: true
205# Base collector configuration.
206# Supports templating. To escape existing instances of {{ }}, use {{` <original content> `}}.
207# For example, {{ REDACTED_EMAIL }} becomes {{` {{ REDACTED_EMAIL }} `}}.
212 # The health_check extension is mandatory for this chart.
213 # Without the health_check extension the collector will fail the readiness and liveness probes.
214 # The health_check extension can be modified, but should never be removed.
216 endpoint: ${env:MY_POD_IP}:13133
219 # Default memory limiter configuration for the collector based on k8s resource limits.
221 # check_interval is the time between measurements of memory usage.
223 # By default limit_mib is set to 80% of ".Values.resources.limits.memory"
225 # By default spike_limit_mib is set to 25% of ".Values.resources.limits.memory"
226 spike_limit_percentage: 25
231 endpoint: ${env:MY_POD_IP}:14250
233 endpoint: ${env:MY_POD_IP}:14268
235 endpoint: ${env:MY_POD_IP}:6831
239 endpoint: ${env:MY_POD_IP}:4317
241 endpoint: ${env:MY_POD_IP}:4318
242 # if internalTelemetryViaOTLP.metrics.enabled = true, prometheus receiver will be removed
246 - job_name: opentelemetry-collector
250 - ${env:MY_POD_IP}:8888
252 endpoint: ${env:MY_POD_IP}:9411
256 k8s.namespace.name: "${env:OTEL_K8S_NAMESPACE}"
257 k8s.node.name: "${env:OTEL_K8S_NODE_NAME}"
258 k8s.node.ip: "${env:OTEL_K8S_NODE_IP}"
259 k8s.pod.name: "${env:OTEL_K8S_POD_NAME}"
260 k8s.pod.ip: "${env:OTEL_K8S_POD_IP}"
261 host.name: "${env:OTEL_K8S_NODE_NAME}"
267 host: ${env:MY_POD_IP}
288 # if internalTelemetryViaOTLP.metrics.enabled = true, prometheus receiver will be removed
300# Helm currently has an issue (https://github.com/helm/helm/pull/12879) when using null to remove
301# default configuration from a subchart. The result is that you cannot remove default configuration
302# from `config`, such as a specific receiver or a specific pipeline, when the chart is used as a
305# Until the helm bug is fixed, this field is provided as an alternative when using this chart as a subchart.
306# It is not recommended to use this field when installing the chart directly.
308# When not empty, `alternateConfig` will be used to set the collector's configuration. It has NO default
309# values and IS NOT MERGED with config. Any configuration provided via `config` will be ignored when
310# `alternateConfig` is set. You MUST provide your own collector configuration.
312# Reminder that the healthcheck extension (or something else that provides the same functionality) is required.
314# Components configured by presets will be injected in the same way they are for `config`.
317 # If you want to use the core image `otel/opentelemetry-collector`, you also need to change `command.name` value to `otelcol`.
318 repository: chainreg.biz/chainguard-private/opentelemetry-collector-contrib
319 pullPolicy: IfNotPresent
320 # Overrides the image tag whose default is the chart appVersion.
322 # When digest is set to a non-empty value, images will be pulled by digest (regardless of tag value).
323 digest: sha256:1fce741b83da131275c5a7c84c1d038e45135819da80102f7d4e7f0dc00b0f43
325# OpenTelemetry Collector executable
330 # Specifies whether a service account should be created
332 # Annotations to add to the service account
334 # The name of the service account to use.
335 # If not set and create is true, a name is generated using the fullname template
337 # Automatically mount a ServiceAccount's API credentials?
338 automountServiceAccountToken: true
340 # Specifies whether a clusterRole should be created
341 # Some presets also trigger the creation of a cluster role and cluster role binding.
342 # If using one of those presets, this field is no-op.
344 # Annotations to add to the clusterRole
345 # Can be used in combination with presets that create a cluster role.
347 # The name of the clusterRole to use.
348 # If not set a name is generated using the fullname template
349 # Can be used in combination with presets that create a cluster role.
351 # A set of rules as documented here : https://kubernetes.io/docs/reference/access-authn-authz/rbac/
352 # Can be used in combination with presets that create a cluster role to add additional rules.
365 # Annotations to add to the clusterRoleBinding
366 # Can be used in combination with presets that create a cluster role binding.
368 # The name of the clusterRoleBinding to use.
369 # If not set a name is generated using the fullname template
370 # Can be used in combination with presets that create a cluster role binding.
372podSecurityContext: {}
377topologySpreadConstraints: []
378# Allows for pod scheduler prioritisation
380# Allows for pod to use a specific runtime class, e.g. gvisor, kata-containers
381# Also useful for the pod security admissions plugins that rely on runtimeClassName
383terminationGracePeriodSeconds: 30
384# This also supports template content, which will eventually be converted to yaml.
386# This also supports template content, which will eventually be converted to yaml.
388# This also supports template content, which will eventually be converted to yaml.
390# This also supports template content, which will eventually be converted to yaml.
392# This also supports template content, which will eventually be converted to yaml.
394# Configuration for ports
395# nodePort is also allowed
436 # The metrics port is disabled by default. However you need to enable the port
437 # in order to use the ServiceMonitor (serviceMonitor.enabled) or PodMonitor (podMonitor.enabled).
442# When enabled, the chart will set the GOMEMLIMIT env var to 80% of the configured resources.limits.memory.
443# If no resources.limits.memory are defined then enabling does nothing.
444# It is HIGHLY recommend to enable this setting and set a value for resources.limits.memory.
446# Container resize policy for in-place resource resize (Kubernetes >= 1.27).
447# https://kubernetes.io/docs/concepts/workloads/autoscaling/#in-place-resizing
451# restartPolicy: NotRequired
452# - resourceName: memory
453# restartPolicy: RestartContainer
455# Resource limits & requests.
456# It is HIGHLY recommended to set resource limits.
463enableConfigChecksumAnnotation: true
466# Common labels to add to all otel-collector resources. Evaluated as a template.
468# app.kubernetes.io/part-of: my-app
470# Host networking requested for this pod. Use the host's network namespace.
472# Enable sharing the host's PID namespace with the pod.
473# WARNING: This grants visibility into all host processes and should only be enabled when required.
475# Adding entries to Pod /etc/hosts with HostAliases
476# https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/
482# Pod DNS policy ClusterFirst, ClusterFirstWithHostNet, None, Default, None
484# Custom DNS config. Required when DNS policy is None.
486# Custom kube scheduler name.
488# only used with deployment and statefulset modes.
490revisionHistoryLimit: 10
492# List of extra sidecars to add.
493# This also supports template content, which will eventually be converted to yaml.
502# image: busybox:latest
507# List of init container specs, e.g. for copying a binary to be executed as a lifecycle hook.
508# This also supports template content, which will eventually be converted to yaml.
509# Another usage of init containers is e.g. initializing filesystem permissions to the OTLP Collector user `10001` in case you are using persistence and the volume is producing a permission denied error for the OTLP Collector container.
513# image: busybox:latest
523# image: busybox:latest
527# - 'chown -R 10001: /var/lib/storage/otc' # use the path given as per `extensions.file_storage.directory` & `extraVolumeMounts[x].mountPath`
529# - name: opentelemetry-collector-data # use the name of the volume used for persistence
530# mountPath: /var/lib/storage/otc # use the path given as per `extensions.file_storage.directory` & `extraVolumeMounts[x].mountPath`
532# Pod lifecycle policies.
541# liveness probe configuration
542# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
545 # Number of seconds after the container has started before startup, liveness or readiness probes are initiated.
546 # initialDelaySeconds: 1
547 # How often in seconds to perform the probe.
549 # Number of seconds after which the probe times out.
551 # Minimum consecutive failures for the probe to be considered failed after having succeeded.
552 # failureThreshold: 1
553 # Duration in seconds the pod needs to terminate gracefully upon probe failure.
554 # terminationGracePeriodSeconds: 10
558# readiness probe configuration
559# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
562 # Number of seconds after the container has started before startup, liveness or readiness probes are initiated.
563 # initialDelaySeconds: 1
564 # How often (in seconds) to perform the probe.
566 # Number of seconds after which the probe times out.
568 # Minimum consecutive successes for the probe to be considered successful after having failed.
569 # successThreshold: 1
570 # Minimum consecutive failures for the probe to be considered failed after having succeeded.
571 # failureThreshold: 1
575# startup probe configuration
576# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
579# Number of seconds after the container has started before startup probes are initiated.
580# initialDelaySeconds: 1
581# How often in seconds to perform the probe.
583# Number of seconds after which the probe times out.
585# Minimum consecutive failures for the probe to be considered failed after having succeeded.
587# Duration in seconds the pod needs to terminate gracefully upon probe failure.
588# terminationGracePeriodSeconds: 10
594 # Enable the creation of a Service.
595 # By default, it's enabled on mode != daemonset.
596 # However, to enable it on mode = daemonset, its creation must be explicitly enabled
599 # Supported values: PreferClose (deprecated in K8s 1.33+), PreferSameZone, PreferSameNode
600 # trafficDistribution: PreferClose
602 # loadBalancerIP: 1.2.3.4
603 # loadBalancerSourceRanges: []
605 # By default, Service of type 'LoadBalancer' or 'NodePort' will be created setting 'externalTrafficPolicy: Cluster'
606 # unless other value is explicitly set.
607 # Possible values are Cluster or Local (https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip)
608 # externalTrafficPolicy: Cluster
610 # By default, Service will be created setting 'internalTrafficPolicy: Local' on mode = daemonset
611 # unless other value is explicitly set.
612 # Setting 'internalTrafficPolicy: Cluster' on a daemonset is not recommended
613 # internalTrafficPolicy: Cluster
617 # ingressClassName: nginx
619 # - host: collector.example.com
625 # - secretName: collector-tls
627 # - collector.example.com
629 # Additional ingresses - only created if ingress.enabled is true
630 # Useful for when differently annotated ingress services are required
631 # Each additional ingress needs key "name" set to something unique
632 additionalIngresses: []
634 # ingressClassName: nginx
637 # - host: collector.example.com
643 # - secretName: collector-tls
645 # - collector.example.com
646# Gateway API HTTPRoute. An alternative to ingress for exposing the
647# collector's HTTP-based receivers through a Gateway API implementation.
648# Requires the Gateway API CRDs to be installed in the cluster.
651 # HTTPRoute apiVersion (defaults to "gateway.networking.k8s.io/v1" when empty)
654 # parentRefs reference the Gateway(s) this HTTPRoute is attached to
657 # namespace: gateway-system
658 # sectionName: otlp-http
660 # hostnames matched against the HTTP Host header to select this route
662 # - collector.example.com
664 # rules associate request matches with a backend port on the collector
665 # service. backendRefs "name" defaults to the collector service when omitted.
675 # The pod monitor by default scrapes the metrics port.
676 # The metrics port needs to be enabled as well.
681 # additional labels for the PodMonitor
683 # release: kube-prometheus-stack
685 # The service monitor by default scrapes the metrics port.
686 # The metrics port needs to be enabled as well.
691 # additional labels for the ServiceMonitor
693 # release: kube-prometheus-stack
694 # Used to set relabeling and metricRelabeling configs on the ServiceMonitor
695 # https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
697 metricRelabelings: []
698 # Sets a sample limit on the ServiceMonitor
700# PodDisruptionBudget is used only if mode is "deployment" or "statefulset"
706# autoscaling is used only if mode is "deployment" or "statefulset"
712 targetCPUUtilizationPercentage: 80
713 # targetMemoryUtilizationPercentage: 80
714 # Supply an array of custom metrics to be used for autoscaling. It includes externalMetrics, objectMetrics, and podsMetrics.
715 additionalMetrics: []
718 # When 'mode: daemonset', maxSurge cannot be used when hostPort is set for any of the ports
721 strategy: RollingUpdate
725 # Create default rules for monitoring the collector
728 ## Additional labels for PrometheusRule alerts
729 additionalRuleLabels: {}
730 ## Additional annotations for PrometheusRule alerts
731 additionalRuleAnnotations: {}
732 # additional labels for the PrometheusRule
735 # volumeClaimTemplates for a statefulset
736 volumeClaimTemplates: []
737 podManagementPolicy: "Parallel"
738 # Controls if and how PVCs created by the StatefulSet are deleted. Available in Kubernetes 1.23+.
739 persistentVolumeClaimRetentionPolicy:
745 # Annotations to add to the NetworkPolicy
747 # Configure the 'from' clause of the NetworkPolicy.
748 # By default this will restrict traffic to ports enabled for the Collector. If
749 # you wish to further restrict traffic to other hosts or specific namespaces,
750 # see the standard NetworkPolicy 'spec.ingress.from' definition for more info:
751 # https://kubernetes.io/docs/reference/kubernetes-api/policy-resources/network-policy-v1/
753 # # Allow traffic from any pod in any namespace, but not external hosts
754 # - namespaceSelector: {}
755 # # Allow external access from a specific cidr block
757 # cidr: 192.168.1.64/32
758 # # Allow access from pods in specific namespaces
759 # - namespaceSelector:
761 # - key: kubernetes.io/metadata.name
767 # Add additional ingress rules to specific ports
768 # Useful to allow external hosts/services to access specific ports
769 # An example is allowing an external prometheus server to scrape metrics
771 # See the standard NetworkPolicy 'spec.ingress' definition for more info:
772 # https://kubernetes.io/docs/reference/kubernetes-api/policy-resources/network-policy-v1/
773 extraIngressRules: []
779 # cidr: 192.168.1.64/32
781 # Restrict egress traffic from the OpenTelemetry collector pod
782 # See the standard NetworkPolicy 'spec.egress' definition for more info:
783 # https://kubernetes.io/docs/reference/kubernetes-api/policy-resources/network-policy-v1/
786 # - namespaceSelector: {}
788 # cidr: 192.168.10.10/24
792# Allow containers to share processes across pod namespace
793shareProcessNamespace: false