You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what you expected:
Expected pods in selected namespace to start with the tracing injected. Instead they fail with the following error: Error creating: pods "my-pod-name-here" is forbidden: violates PodSecurity "baseline:latest": hostPath volumes (volume "datadog")
Agent Environment
7.56.1
Describe what happened:
Tested enabling Single Step APM Instrumentation in kubernetes with the Datadog Helm Chart: https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/single-step-apm/?tab=kubernetespreview#specifying-at-the-cluster-level
Describe what you expected:
Expected pods in selected namespace to start with the tracing injected. Instead they fail with the following error:
Error creating: pods "my-pod-name-here" is forbidden: violates PodSecurity "baseline:latest": hostPath volumes (volume "datadog")
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc):
AWS EKS.
It is probably the same as reported in issue #28274 , but for Single Step APM Instrumentation there is no option to set
socketEnabled: false
The text was updated successfully, but these errors were encountered: