Console is running in a Kubernetes cluster, and you need to deploy Defenders on nodes within this cluster. Which option shows the steps to deploy the…

To deploy Defenders on the same Kubernetes cluster as the Console, the standard and recommended method is using a DaemonSet. This ensures each node gets a Defender. The deployment manifest is generated from the Console UI (Manage > Defenders > Deploy). When prompted for the Console's address, the Kubernetes service name for the Console, which is twistlock-console by default, should be used. This provides a stable endpoint for Defenders to connect to. The generated DaemonSet YAML file is then applied to the cluster, typically in the twistlock namespace.

A. Using a specific pod name is incorrect because pods are ephemeral; the stable Kubernetes service name must be used for reliable communication.

B. Cloud discovery and auto-protection is a different deployment method and not the direct manual deployment process described.

D. The curl | bash script is for single Docker hosts, not for deploying across a Kubernetes cluster using a DaemonSet.

1. Palo Alto Networks

"Prisma Cloud Compute - Administrator's Guide

" Version Self-Hosted 32.01. The "Deploy Defenders" section for Kubernetes details the process of generating a DaemonSet YAML file from the Console. It specifies using the Console's service name (default: twistlock-console) as the address for the Defenders to connect to.