Microsoft Defender for Cloud
Identity protection

Install Defender for Containers sensor using Helm

In brief

The page now links to prerequisites and explicitly directs administrators to verify that Helm and curl are installed before deploying Defender for Containers.

What Defender admins need to know

Administrators can use the added checks to validate deployment prerequisites before installation.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Install Defender for Containers sensor using Helm

To control deployment and upgrade timing across your Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Google Kubernetes Engine (GKE) clusters, install and configure the Microsoft Defender for Containers sensor by using Helm. Before you begin, make sure you meet the prerequisites, including Helm availability, Defender for Containers plan enablement, and cluster access.

Defender for Containers supports multiple sensor deployment models, including automatic provisioning and Helm-based installation. Helm-based deployment gives you more control over versioning and upgrade timing, but you manage some of the operational work. When you use Helm-based deployment, consider:

  • Make sure helm and curl are installed and available in your command-line environment.

    To check whetherconfirm that Helm and curl are installed and available before you deploy Defender for Containers, run the tools are available, run:following commands:

    helm version
    curl --version
    
  • Implement all prerequisite requirements for the Defender for Containers sensor as described in the Defender sensor network requirements.