Option A: Admission controllers in Kubernetes function as webhooks that the API server invokes during resource creation. They can be either mutating webhooks, which modify API requests, or validating webhooks, which approve or deny them based on security policies. Falcon Cloud Security leverages this functionality to enforce security policies on workload deployment, preventing misconfigurations, vulnerabilities, and non-compliant images from being deployed.
Option B: Admission controllers do not modify etcd directly. They operate at the request validation stage before data is stored in etcd, ensuring that only compliant and secure configurations proceed.
Option C: Admission controllers are not deployed as sidecar containers in every pod. Instead, they act as centralized services that interact with the API server to validate and enforce security rules before pod creation.
Option D: API requests are not manually approved before admission controllers take effect.
Instead, the webhook-based controller evaluates and either modifies or denies requests automatically.