Features · GCP
GCP probes — shipped.
10 probes via a live google.golang.org/api wrapper: Cloud SQL, GKE control-plane + node pools, IAM service accounts, Subnets, Load Balancer backends, managed certificates, GCS public-access, KMS. GKE Workload Identity — zero long-lived credentials. Read-only by design.
10 GCP cloud probes, modelled on the AWS set, using a live google.golang.org/api wrapper and GKE Workload Identity (off by default; cloud.gcp.enabled=true; per-probe toggles under cloud.gcp.probes). Cloud SQL disk-utilization is measured live via the Cloud Monitoring API (the probe skips the storage check when no recent datapoint exists rather than reporting 0%). Subnet IP-utilization is the one honest gap: GCP's Compute API exposes no cheap used-IP count, so the probe runs capacity-only — it flags primary CIDRs smaller than /26 (threshold configurable) and points you at Network Analyzer for the real allocation ratio. Everything else (Cloud SQL state/backup, GKE control-plane + node pools, IAM service accounts, LB backend health, managed-cert status, GCS public-access, KMS) is fetched live. Read-only by design.