What is a key requirement for deploying the CrowdStrike Kubernetes Admission Controller to monitor and secure Kubernetes workloads?

Question

Options

• AThe Admission Controller requires the Mutating Admission Webhook configuration to be enabled in
• BThe Admission Controller must run with root-level permissions inside a privileged container.
• CThe Admission Controller requires a dedicated namespace in the Kubernetes cluster.
• DThe Admission Controller must be deployed as a DaemonSet on every node.

• A
  94% (51)
• C
  4% (2)
• D
  2% (1)

Explanation

Option A: The CrowdStrike Kubernetes Admission Controller uses the Mutating Admission Webhook to intercept and modify requests to the Kubernetes API server. This webhook allows the controller to enforce security policies and inject the required sensor configurations into pods at creation time. Ensuring the Mutating Admission Webhook configuration is enabled is a critical setup step for proper functionality. Option B: The Admission Controller does not require root-level or privileged permissions. It relies on webhook functionality to perform its operations and does not interact directly with host-level Option C: While namespaces are often used for logical organization, the Admission Controller does not necessarily require a dedicated namespace. It can be deployed in any namespace, depending on the user's configuration preferences. Option D: The Admission Controller is not deployed as a DaemonSet; instead, it operates as a webhook server integrated with the Kubernetes API server. DaemonSets are typically used for agents that need to run on every node, such as logging or monitoring tools.

No community discussion yet for this question.