Google Cloud

ScraperHealth Check

Mission Control integrates with Google Cloud Platform to provide visibility into your cloud infrastructure.

---

Scraper

Discover and catalog GCP resources with full change history and relationships.

Use cases:

• Discover and catalog Compute Engine VMs, Cloud SQL instances, GKE clusters, and other GCP resources
• Track configuration changes across projects and folders
• Correlate GCP resources with GKE workloads and Terraform state
• Build relationships between GCP services and their dependencies
• Support organization-wide visibility with folder-based access

---

Health Check

Monitor GCP services and endpoints with health checks.

Use cases:

• Monitor Cloud Storage bucket availability and object health
• Check Cloud SQL database connectivity and status
• Verify GKE cluster health and node status

Getting Started

Prerequisites

To enable the GCP integration you need:

• Mission Control installed
• kubectl access to the Mission Control instance
• GCP service account credentials or GKE Workload Identity configured for the config-db service.

1. Install the mission-control-gcp chart

   Helm

   helm install mission-control-gcp flanksource/mission-control-gcp \
    --set project=<your-project-name> \
    -n mission-control --wait 

   Flux

   apiVersion:  helm.toolkit.fluxcd.io/v2
   kind: HelmRelease
   metadata:
     name: mission-control-gcp
     namespace: mission-control
   spec:
     chart:
       spec:
         chart: mission-control-gcp
         sourceRef:
           kind: HelmRepository
           name: flanksource
           namespace: mission-control
     interval: 5m
   values:
     project: <your-project-name>
   values.yaml

   • connection:
   • credentials:
     • value: string
     • valueFrom:
       • configMapKeyRef:
         • key: string
         • name: string
       • helmRef:
         • key: string
         • name: string
       • secretKeyRef:
         • key: string
         • name: string
       • serviceAccount: string
   • endpoint: string
   • exclude[]:

     list of googleapis to exclude from scraping examples: - compute.googleapis.com/InstanceSettings - serviceusage.googleapis.com/Service
     - list of googleapis to exclude from scraping examples: - compute.googleapis.com/InstanceSettings - serviceusage.googleapis.com/Service
   • global:

     Global values are values that can be accessed from any chart or subchart by exactly the same name.
     - Global values are values that can be accessed from any chart or subchart by exactly the same name.
   • include[]:

     list of googleapis to include in scraping examples: - compute.googleapis.com/Instance - compute.googleapis.com/Network
     - list of googleapis to include in scraping examples: - compute.googleapis.com/Instance - compute.googleapis.com/Network
   • labels: - list of labels to add the Scrape config
   • project:
   • scraper:
     • name: string (default: "gcp")
     • pluginName: string (default: "gcp")
   • skipTLSVerify: boolean
   • transform:

When you go to the catalog now, you can now see all the GCP Resources

Next Steps

GCP Scraper

GCP config scraper configuration options

AWS Integration

Learn about AWS resource scraping