Immutable solution version
Prisma Defender daemonset on EKS needs --privileged and --cri in the twistcli export, or it never registers
Complete solution
When exporting the Defender daemonset with twistcli defender export kubernetes, always pass --privileged and --cri.
Prisma Defender daemonset on EKS needs --privileged and --cri in the twistcli export, or it never registers
TL;DR
When exporting the Defender daemonset with twistcli defender export kubernetes, always pass --privileged and --cri. The Defender must run privileged and must use the Container Runtime Interface to protect the other pods' containers; without those flags the daemonset deploys, looks healthy, and never shows up in the console. After redeploying with both flags, confirm one defender pod per node and check Manage Defenders in the console.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
Tool: Prisma. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Community thread on live.paloaltonetworks.com (16 replies, ~15k views): a user triaged an EKS cluster where the Prisma Defender daemonset deployed but never appeared in the console. The verified resolution from the reporter: the daemonset YAML generated by twistcli defender export was missing two options, and without them the Defender cannot protect the other pods' containers.
Evidence
Source: Community thread on live.paloaltonetworks.com (16 replies, ~15k views): a user triaged an EKS cluster where the Prisma Defender daemonset deployed but never appeared in the console. The verified resolution from the reporter: the daemonset YAML generated by twistcli defender export was missing two options, and without them the Defender cannot protect the other pods' containers.
Verified resolution: When exporting the Defender daemonset with twistcli defender export kubernetes, always pass --privileged and --cri. The Defender must run privileged and must use the Container Runtime Interface to protect the other pods' containers; without those flags the daemonset deploys, looks healthy, and never shows up in the console. After redeploying with both flags, confirm one defender pod per node and check Manage > Defenders in the console.
Source URL: https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/how-to-triage-an-eks-cluster-with-prisma-defender-daemon-set-not/m-p/521403/highlight/true
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_pxCKOtT3HIWySgH5gn7U4g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Prisma Defender daemonset on EKS needs --privileged and --cri in the twistcli export, or it never registers <span>— Vectle</span></a>