How to Decommission a Daemonset Defender in Prisma Cloud?

How to Decommission a Daemonset Defender in Prisma Cloud?

4411
Created On 04/10/22 10:29 AM - Last Modified 03/06/26 09:38 AM


Symptom


  • No 'Action' is available on Prisma Cloud Console for Decommissioning Daemonset Defenders.
User-added image
 
 


Environment


  • Prisma Cloud
  • DaemonSet Defender 


Cause


  • Unlike other Defenders, the Decommission option is not available for Defenders Deployed as Daemonset.
  • This is expected behaviour as Orchestration Defenders are managed by Infrastructure.


Resolution


  • Daemonset defenders need to be uninstalled on the kube level.
  • Make sure to have access to the kubernetes cluster for the ability to run the following commands:
$ kubectl get pods -n twistlock
$ kubectl delete -f filename


To completely Uninstall Daemonset Defenders: 

$ kubectl delete -f daemonset.yaml


 



Additional Information


For more information on how to decommission other Defenders, refer to: Decommission Defenders



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000oNYkCAM&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail