This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

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.

    Prerequisites

    1. Install a GKE cluster in Autopilot mode.

    2. Connect the GKE cluster.

    3. Install your workload.

    Deploy Sysdig Agent

    Sysdig recommends using Helm to install Sysdig agent in kubernetes environments. After connecting to the GKE cluster, use the sysdig-deplpy chart to install Sysdig agent.

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

    Verify Agent Installation in Sysdig Secure

    1. Log in to Sysdig Secure.

      See SaaS Regions and IP Ranges and identify the correct domain URL associated with your Sysdig application and region.

    2. Navigate to Integrations > Sysdig Agents.

      The Sysdig Agents page list all the agents installed your environment. For more information, see Sysdig Agents.

    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 https://app.sysdigcloud.com.

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

      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.