Overview
Google Cloud operations covering Compute Engine, Cloud Run for containers, BigQuery for analytics, Cloud Functions, and GKE for Kubernetes.
Capabilities
- Compute Engine VM management
- Cloud Run container deployment
- BigQuery SQL analytics
- Cloud Functions serverless
- GKE cluster management
- IAM and service accounts
- Cost management and committed use
When to Use
Trigger phrases:
"gcp ops"
"Google Cloud operations — Compute Engine, Cloud Run, BigQuery, Cloud Functions, "
GCP infrastructure management
Data analytics with BigQuery
Container workloads on GKE
Serverless with Cloud Run
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Pseudo Code
The gcp-ops workflow follows a standard pipeline pattern.
Core flow:
# gcp-ops primary flow
input = prepare(raw_data)
result = process(input, config={bigquery, cloud, compute, engine, functions})
validate(result)
deliver(result)
Error handling:
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
Cloud Run Deploy
gcloud run deploy my-service --image gcr.io/project/image --region us-central1 --allow-unauthenticated --memory 512Mi
Common Patterns
- Use service accounts with least privilege
- Preemptible VMs for batch work
- BigQuery slots for predictable cost
- Cloud Run concurrency tuning
How to Use
- Define infrastructure as code (Terraform, CloudFormation, Pulumi)
- Review changes through PR process before applying
- Configure monitoring and alerting for critical paths
- Set up secrets management (Vault, AWS Secrets Manager, etc.)
- Document runbooks for deployment, rollback, and incident response
- Test disaster recovery procedures regularly
Red Flags
- Infrastructure changes without review: Unreviewed changes cause outages — use PRs for infra code
- No rollback strategy: Every deployment needs a tested rollback plan before it runs
- Secrets in configuration files: Secrets in YAML/JSON get committed to version control
- Missing monitoring and alerting: Without monitoring, outages go undetected until users report them
- No documentation for runbooks: Without runbooks, on-call engineers waste time re-discovering procedures
Verification
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
Anti-Rationalization Table
| Rationalization |
Reality |
| "Manual deployments are fine" |
Manual deployments are error-prone and不可 repeatable. Automate. |
| "We do not need monitoring" |
Without monitoring, you are flying blind. Add observability from day one. |
| "Infrastructure as code is overkill" |
IaC enables reproducibility, version control, and disaster recovery. |
1---2name: gcp-ops3description: Use when google Cloud operations — Compute Engine, Cloud Run, BigQuery,4 Cloud Functions, GKE, IAM. Use when working with gcp ops.5domain: devops6author: oyi777license: Apache-2.08subdomain: devops9tags:10- ci-cd11- devops12- gcp13- infrastructure14- ops15version: 1.0.016category: devops17metadata:18 source: https://skillmd.com/skills/oyi77/gcp-ops19---20212223## Overview2425Google Cloud operations covering Compute Engine, Cloud Run for containers, BigQuery for analytics, Cloud Functions, and GKE for Kubernetes.2627## Capabilities2829- Compute Engine VM management30- Cloud Run container deployment31- BigQuery SQL analytics32- Cloud Functions serverless33- GKE cluster management34- IAM and service accounts35- Cost management and committed use3637## When to Use38**Trigger phrases:**39- "gcp ops"40- "Google Cloud operations — Compute Engine, Cloud Run, BigQuery, Cloud Functions, "414243- GCP infrastructure management44- Data analytics with BigQuery45- Container workloads on GKE46- Serverless with Cloud Run4748## When NOT to Use4950- Task is outside your authorization scope51- You need to implement controls (use implementing-* skills)52- Task is about analysis, not action (use analyzing-* skills)53- You don't have access to target systems54- Task requires compliance expertise (consult professionals)55- Task is about defense, not offense (use defensive skills)565758## Pseudo Code5960The gcp-ops workflow follows a standard pipeline pattern.6162Core flow:63```64# gcp-ops primary flow65input = prepare(raw_data)66result = process(input, config={bigquery, cloud, compute, engine, functions})67validate(result)68deliver(result)69```7071Error handling:72```73on error:74 log(error_details)75 retry_with_backoff(max=3)76 if still_failing: alert_and_escalate()77```787980### Cloud Run Deploy81```bash82gcloud run deploy my-service --image gcr.io/project/image --region us-central1 --allow-unauthenticated --memory 512Mi83```8485## Common Patterns8687- Use service accounts with least privilege88- Preemptible VMs for batch work89- BigQuery slots for predictable cost90- Cloud Run concurrency tuning9192## How to Use93941. Define infrastructure as code (Terraform, CloudFormation, Pulumi)952. Review changes through PR process before applying963. Configure monitoring and alerting for critical paths974. Set up secrets management (Vault, AWS Secrets Manager, etc.)985. Document runbooks for deployment, rollback, and incident response996. Test disaster recovery procedures regularly100101## Red Flags102103- **Infrastructure changes without review**: Unreviewed changes cause outages — use PRs for infra code104- **No rollback strategy**: Every deployment needs a tested rollback plan before it runs105- **Secrets in configuration files**: Secrets in YAML/JSON get committed to version control106- **Missing monitoring and alerting**: Without monitoring, outages go undetected until users report them107- **No documentation for runbooks**: Without runbooks, on-call engineers waste time re-discovering procedures108109## Verification110111- [ ] Skill output matches expected behavior112113## Process1141151. Analyze the task requirements1162. Apply domain expertise1173. Verify output quality118119## Anti-Rationalization Table120121| Rationalization | Reality |122|---|---|123| "Manual deployments are fine" | Manual deployments are error-prone and不可 repeatable. Automate. |124| "We do not need monitoring" | Without monitoring, you are flying blind. Add observability from day one. |125| "Infrastructure as code is overkill" | IaC enables reproducibility, version control, and disaster recovery. |