GCP

Mission Control integrates with Google Cloud Platform to scrape and monitor your GCP cloud resources. The integration supports:

• GCP project monitoring via project ID
• Organization and folder-based access
• Configurable exclusions and transformations
• Authentication via service account keys or Workload Identity
• Custom connection settings

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")
   • skipTLSVerify: boolean
   • transform:

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

Next Steps

ScrapeConfig

CRD

GCP Cloud Storage

Check GCS buckets and objects

health-check