-
Notifications
You must be signed in to change notification settings - Fork 155
fix(gpu): force disable eBPF probes #3302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -127,6 +127,21 @@ func configureSystemProbe(managers feature.PodTemplateManagers) { | |
| // add the env var to the core agent as well, to prevent config mismatches in runtime | ||
| managers.EnvVar().AddEnvVarToContainer(apicommon.CoreAgentContainerName, enableSPEnvVar) | ||
|
|
||
| // In privileged mode the eBPF probes are disabled, as GPU monitoring relies on | ||
| // the privileged host access rather than the eBPF probes. | ||
| disableEBPFProbesEnvVar := &corev1.EnvVar{ | ||
| Name: DDEnableEBPFProbesEnvVar, | ||
| Value: "false", | ||
| } | ||
|
|
||
| // disable the eBPF probes in system-probe | ||
| managers.EnvVar().AddEnvVarToContainer(apicommon.SystemProbeContainerName, disableEBPFProbesEnvVar) | ||
|
|
||
| // add the env var to the core agent as well, so both containers agree that the | ||
| // eBPF probes are disabled and the core GPU check does not poll a system-probe | ||
| // module that has the probes turned off | ||
| managers.EnvVar().AddEnvVarToContainer(apicommon.CoreAgentContainerName, disableEBPFProbesEnvVar) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. suggestion (non-blocking): this hard-codes the probes off with no first-class opt-out, which is the right default given the GB300 crashes. Worth documenting the escape hatch that already exists: feature config runs before |
||
|
|
||
| // annotations | ||
| managers.Annotation().AddAnnotation(common.SystemProbeAppArmorAnnotationKey, common.SystemProbeAppArmorAnnotationValue) | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion (non-blocking): this force-disables the probes, which makes the
privilegedModefield doc stale. The marker atapi/datadoghq/v2alpha1/datadogagent_types.go:721still reads "PrivilegedMode enables GPU Probe module in System Probe" — accurate for the module, but the probes it implies are now off by default. That comment is the source for both generated docs (docs/configuration_public.md:235,docs/configuration.v2alpha1.md:136), so they drift with it. Update the marker to note the eBPF probes are disabled by default and privileged mode is retained for cgroup permission patching, then runmake generate && make manifestsso both generated docs move in lockstep.