Skip to content
3 changes: 3 additions & 0 deletions charts/datadog/templates/_container-host-profiler.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,9 @@
mountPath: {{ template "datadog.confPath" . }}/auth
readOnly: true
{{- end }}
- name: {{ include "datadog.agentRunVolumeName" . }}
mountPath: /opt/datadog-agent/run
readOnly: false
- name: tmpdir
mountPath: /tmp
readOnly: false # Need RW for tmp directory
Expand Down
3 changes: 3 additions & 0 deletions charts/datadog/templates/_container-otel-agent.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,9 @@
- name: otelconfig
mountPath: {{ template "datadog.otelconfPath" . }}
readOnly: true
- name: {{ include "datadog.agentRunVolumeName" . }}
mountPath: /opt/datadog-agent/run
readOnly: false
Comment on lines +110 to +112

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Gate the run mount for Windows otel-agent pods

When targetSystem=windows and datadog.otelCollector.enabled=true with log collection left at its default disabled state, this helper expands to datadogrun, but daemonset-volumes-windows never defines a datadogrun volume; it only creates pointerdir when logs are enabled. The rendered DaemonSet therefore contains an otel-agent volumeMount with no matching volume and Kubernetes will reject the pod, so this mount needs a Windows-specific volume/path or should be limited to Linux.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{{- if eq .Values.targetSystem "linux" }}
{{- if not .Values.providers.gke.autopilot }}
- name: procdir
Expand Down
Loading