Skip to content

[codex] Add Cloud Security Kubernetes DaemonSet setup#37634

Draft
cyrbouchiat wants to merge 1 commit into
masterfrom
codex/cloud-security-kubernetes-daemonset
Draft

[codex] Add Cloud Security Kubernetes DaemonSet setup#37634
cyrbouchiat wants to merge 1 commit into
masterfrom
codex/cloud-security-kubernetes-daemonset

Conversation

@cyrbouchiat

Copy link
Copy Markdown
Contributor

What changed

  • Added a DaemonSet tab to the Cloud Security Kubernetes setup page.
  • Documented the Cloud Security env vars required for Misconfigurations, Vulnerability Management, container image mount scanning, and runtime package tracking.
  • Clarified that the same env var block must be applied to each Agent pod container in a DaemonSet: agent, security-agent, and system-probe.
  • Added a DaemonSet option to the Runtime Package Tracking section.

Why

The Kubernetes Cloud Security setup page covered Operator and Helm, but not direct DaemonSet configuration. Customers using DaemonSets need explicit env var instructions, especially for DD_COMPLIANCE_CONFIG_ENABLED, DD_COMPLIANCE_CONFIG_HOST_BENCHMARKS_ENABLED, DD_SBOM_CONTAINER_IMAGE_USE_MOUNT, and DD_SBOM_ENRICHMENT_USAGE_ENABLED.

Validation

  • Verified all required env vars are present in each DaemonSet container shown.
  • Verified Hugo tab shortcode counters balance.
  • Ran git diff --check.
  • Confirmed only content/en/security/cloud_security_management/setup/agent/kubernetes.md changed.

@github-actions

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@cyrbouchiat cyrbouchiat force-pushed the codex/cloud-security-kubernetes-daemonset branch from a486c10 to 40340e7 Compare June 19, 2026 11:42

Copy link
Copy Markdown
Contributor Author

Updated after review to avoid implying the Workload Protection docs already had an equivalent expanded block per container. The DaemonSet instructions now show one env var block and explicitly say to copy it into each Agent container (agent, security-agent, and system-probe), matching the Agent team guidance while keeping the snippet closer to the existing DaemonSet docs style.

Add `DD_SBOM_ENRICHMENT_USAGE_ENABLED` to the `env` section of every Agent container in your `daemonset.yaml` file, including `agent`, `security-agent`, and `system-probe`:

```yaml
- name: DD_SBOM_ENRICHMENT_USAGE_ENABLED

@agentzzk agentzzk Jun 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We'll also need to add a note for customers to add hostPID: true when manually managing DaemonSet through env

Also, I believe we need to set DD_SBOM_CONTAINER_IMAGE_ENABLED here too, similar to containerImage.enabled for Helm or Operator? cc @lebauce

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated. I added hostPID: true to the DaemonSet pod spec snippet for mount-based container image scanning, and updated the Runtime Package Tracking DaemonSet snippet to include DD_SBOM_ENABLED=true, DD_SBOM_CONTAINER_IMAGE_ENABLED=true, and DD_SBOM_ENRICHMENT_USAGE_ENABLED=true for every Agent container.

@cyrbouchiat cyrbouchiat force-pushed the codex/cloud-security-kubernetes-daemonset branch 2 times, most recently from 07a7650 to fcc7205 Compare June 22, 2026 07:46
@cyrbouchiat cyrbouchiat force-pushed the codex/cloud-security-kubernetes-daemonset branch from fcc7205 to 165b704 Compare June 22, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants