Installing Sysdig Agent on GKE Autopilot

Autopilot is an operation mode for creating and managing clusters in GKE. In brief, with Autopilot, Google configures and manages the underlying node infrastructure for you. This topic helps you use helm to install Sysdig agent on a GKE cluster installed in Autopilot mode.

NodeAnalyzer is not supported on Autopilot environments.


  1. Install a GKE cluster in Autopilot mode.

  2. Connect the GKE cluster.

  3. Install your workload.

Deploy Sysdig Agent

After connecting to the GKE cluster, you can install the pre-configured Sysdig agent using helm.

To customize the configuration of the agent, see the Sysdig Agent Helm Chart.

  1. Add the Sysdig Agent Helm Chart repository:

    $ helm repo add sysdig `
  2. Create a namespace for the Sysdig agent:

    $ kubectl create ns sysdig
  3. Install the Sysdig agent chart:

    $ helm install agent --namespace sysdig --set sysdig.accessKey=$SYSDIG_AGENT_KEY --set sysdig.settings.collector=$COLLECTOR_URL sysdig/sysdig --set gke.autopilot=true

    Replace the values as follows:

    • $SYSDIG_AGENT_KEY: Use the Sysdig agent key for your Sysdig Platform.

    • $COLLECTOR_URL: The URL is region-dependent in Sysdig SaaS. See Regions and IP Ranges. The Collector URL is custom for on-prem installations.

    Once the installation is complete, you can get started with Sysdig Secure and Sysdig Monitor.

Verify Metrics on the Sysdig Monitor UI

Log in to Sysdig Monitor to verify that the agent deployed and the metrics are detected and collected appropriately.

Given below is one way to do so.

  1. Access Sysdig Monitor:

    SaaS: See SaaS Regions and IP Ranges and identify the correct domain URL associated with your Sysdig application and region. For example, for US East, the URL is

    For other regions, the format is https://<region> Replace <region> with the region where your Sysdig application is hosted. For example, for Sysdig Monitor in the EU, you use

    Log in with your Sysdig user name and password.

  2. Select the Explore tab to see if metrics are displayed.

  3. Verify that kube state metrics and cluster name are working correctly: select the Explore tab and create a grouping by kube_cluster_name and kube_pod_name.

  4. Select an individual container or pod to see the details.

Last modified May 20, 2022