> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-gcp/running-the-groundcover-sensor-on-gke-autopilot.md).

# Running the groundcover sensor on GKE Autopilot

Running the privileged groundcover sensor on GKE Autopilot requires an approved WorkloadAllowlist and Autopilot mode in the chart.

### Requirements

* A GKE Autopilot cluster on **1.32.2-gke.1652000 or later**.
* The groundcover Helm chart with Autopilot support (`agent.gke.autopilot.*`) in version 1.12.90+.

### How it works

1. **Allowlist** — Google stores groundcover's approved sensor allowlist in a managed partner repo (`groundcover/sensor/*`).
2. **Synchronizer** — you install an `AllowlistSynchronizer` (a cluster-scoped CR) that pulls that allowlist into your cluster as a `WorkloadAllowlist`.
3. **Label** — the sensor pod carries `cloud.google.com/matching-allowlist`, which tells Autopilot to match it against the allowlist and admit it.

Enabling `agent.gke.autopilot.enabled` wires up (2) and (3) for you.

### Install

Add to your sensor values:

```yaml
agent:
  gke:
    autopilot:
      enabled: true
      # installs an AllowlistSynchronizer pointing at groundcover's partner repo
      installAllowlistSynchronizer: true
      allowlistRepoPath: "groundcover/sensor/*"
```

If you already manage allowlists yourself, set `installAllowlistSynchronizer: false` and provide your own `AllowlistSynchronizer` .

### Private image mirrors

If you pull the sensor images from your **own private registry** (not `public.ecr.aws/groundcovercom` or `quay.io/groundcover`), reference them **by digest** and pin your workload to that digest:

```
image: registry.example.internal/mirror/sensor@sha256:<digest>
```

A mirror of a groundcover image keeps the **same digest**, and the approved allowlist lists those digests (`containerImageDigests`), so a digest-pinned image is admitted regardless of its registry path. If you mirror a version whose digest isn't in the allowlist yet, ask groundcover to add it.

### Troubleshooting

* **Sensor pods rejected by "GKE Warden"** — the `WorkloadAllowlist` isn't installed yet (check `kubectl get workloadallowlist`) or the matching label is missing. Confirm the `AllowlistSynchronizer` is `Ready`.
* **`… Mismatch …` in the rejection** — the running sensor differs from the approved allowlist (e.g. an extra volume/mount from custom values). Autopilot prints the exact field; align your values or contact groundcover for an updated allowlist.
* See also Google's guide: <https://cloud.google.com/kubernetes-engine/docs/how-to/run-autopilot-partner-workloads>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-gcp/running-the-groundcover-sensor-on-gke-autopilot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.