Agentless scanning support for AKS on ACI and GKE Autopilot - #39591
Merged
BraisCabo-DD merged 4 commits intoSep 2, 2026
Conversation
Contributor
Preview links (active after the
|
Contributor
Author
|
/review |
Contributor
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
Diff is a targeted update to the Kubernetes row of the compatibility table. No blockers or style violations spotted; the Cluster Agent requirement wording is consistent with the existing EKS on Fargate note.
Reviewed 2485c144b2ac26741f9b79a0af18d50c11de7ba6 — workflow run
The support boundaries per platform are unchanged; only the scanning depth for already-supported node types (image-level, not just disk-level) improved.
…caveat Both auto-managed node types now require the Datadog Cluster Agent, mirroring the existing EKS on Fargate requirement. Image streaming on GKE is now supported.
janine-c
approved these changes
Sep 1, 2026
BraisCabo-DD
marked this pull request as ready for review
September 2, 2026 13:19
BraisCabo-DD
deleted the
brais.cabofelpete/aks-gke-kubernetes-scanning-update
branch
September 2, 2026 13:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Agentless Scanning now supports Kubernetes container image scanning on the auto-managed node types that were previously excluded: AKS on Azure Container Instances (ACI) and GKE Autopilot, in addition to the already-supported AKS virtual machines/VMSS and GKE Standard. Both auto-managed types require the Datadog Cluster Agent, the same prerequisite already documented for EKS on Fargate. GKE image streaming is also now supported, so that caveat is removed.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code to research the underlying change (via Slack, the implementation PR, and confirmation from the feature team) and update this doc accordingly.
Additional notes