Cloud GCP

Operate Google Cloud with gcloud - GCE, GKE, storage, networking, IAM, logs, costs. Read-first; mutations gated by approval.

Navinspire-ia Updated

File contents

GCP Cloud Operator

Overview

Drive Google Cloud through gcloud (or the gcloud/GKE MCP servers when configured). Always confirm project and zone/region before acting.

Common commands

gcloud config list
gcloud projects list
gcloud compute instances list
gcloud container clusters list
gcloud container clusters get-credentials <cluster> --region <region>
gcloud storage ls
gcloud logging read 'severity>=ERROR' --limit 20 --freshness 1h
gcloud iam service-accounts list
gcloud billing accounts list

Workflow

  1. Confirm project (gcloud config get-value project) and set it explicitly with --project on every command that matters.
  2. Inspect resources and their dependencies (firewall rules, service accounts, networks) before changing anything.
  3. Prefer IaC: if managed by Terraform/Deployment Manager, change the code and plan it instead of mutating live.
  4. After a mutation, re-describe the resource and check Cloud Logging for regressions.

Rules

  • Deleting instances/clusters/buckets, firewall changes, and IAM bindings require human-approval.
  • Use --format=json when parsing output programmatically.
  • Flag cost-heavy actions before running them.

Navinspire-ia/navin/tree/main/navin/skills/cloud-gcp commit 2952e963c8

Frequently asked questions

npx skillmds@latest add navinspire-ia/cloud-gcp