After deploying the CrowdStrike Kubernetes Sensor in a Kubernetes cluster, some containers are not being monitored, even though the deployment logs indicate a successful installation. What is the most

Question

Options

• AThe Kubernetes cluster uses a container runtime not supported by CrowdStrike.
• BThe cluster's kubelet is misconfigured, preventing the sensor from attaching to containers.
• CThe Kubernetes cluster is running on an unsupported cloud provider.
• DThe sensor DaemonSet is not running on all cluster nodes.

• A
  9% (3)
• B
  3% (1)
• C
  18% (6)
• D
  71% (24)

Explanation

Option A: While a mismatched container runtime can cause monitoring issues, CrowdStrike supports a wide range of container runtimes. If an unsupported runtime were the issue, it would be flagged during deployment, not afterward. Option B: While kubelet misconfiguration could cause container management issues, this would typically prevent container creation or result in broader cluster-wide errors, not selective monitoring failures. Option C: CrowdStrike supports most major cloud providers. Unsupported cloud providers would likely cause deployment issues, not selective monitoring problems. Option D: This is the correct answer because the DaemonSet ensures that the CrowdStrike sensor runs on all nodes in the cluster. If the DaemonSet is not deployed properly across all nodes, workloads on the unaffected nodes will not be monitored, even though the overall installation appears successful.

No community discussion yet for this question.