Skip to content

aktonay/skillz / skills/cloud/gke-basics

gke-basics

Flagged

Plan, create, and configure production-ready Google Kubernetes Engine (GKE) clusters using the golden path Autopilot configuration. Covers Day-0 checklist, Autopilot vs Standard, networking (private clusters, VPC-native, Gateway API), security (Workload Identity, Secret Manager, RBAC hardening), observability, scaling, cost optimization, and AI/ML inference. WHEN: create GKE cluster, provision GKE environment, design GKE networking, secure GKE, optimize GKE cost, GKE autoscaling, GKE inference, GKE upgrade, GKE observability, GKE multi-tenancy, GKE batch, GKE HPC, GKE compute class.

references/core-concepts.md

View on GitHub
# GKE Core Concepts

Google Kubernetes Engine (GKE) is a managed Kubernetes platform for deploying, managing, and scaling containerized applications on Google Cloud infrastructure. It handles cluster provisioning, upgrades, and node management, letting teams focus on workloads rather than infrastructure.

> **MCP Tools:** `list_clusters`, `get_cluster`

## Cluster Modes

| Mode | Who Manages Nodes | Best For |
|------|-------------------|----------|
| **Autopilot** (recommended) | Google — fully managed nodes, scaling, and security | Most workloads. No node-level ops. Pay per pod resource request. |
| **Standard** | You — full control over node pools, OS, machine types | Workloads requiring kernel customization, specific node OS, or DaemonSets not supported by Autopilot |

**Default: Autopilot.** Use Standard only when Autopilot has a documented limitation for your workload.

## Cluster Architecture

- **Regional clusters** (recommended): Control plane replicated across 3 zones. Higher availability, no single-zone failure risk.
- **Zonal clusters**: Single control plane zone. Lower cost, acceptable for dev/test.
- **Private clusters** (golden path default): Nodes have no public IPs. Control plane accessible via private endpoint or DNS endpoint.

## Networking Model

GKE uses **VPC-native** clusters with alias IP ranges:
- Each pod gets a routable IP from the pod CIDR
- Dataplane V2 (eBPF-based) is the golden path default — provides built-in Network Policy enforcement
- Cloud DNS for in-cluster DNS resolution
- Gateway API for ingress/load balancing

## Scaling Model

- **Horizontal Pod Autoscaler (HPA)**: Scales pod replicas based on CPU, memory, or custom metrics
- **Vertical Pod Autoscaler (VPA)**: Recommends or auto-adjusts pod resource requests
- **Cluster Autoscaler / NAP**: Scales nodes to match pod demand (Autopilot handles this automatically)
- **ComputeClasses**: Declarative node selection — machine family, Spot VMs, GPU targeting

## Identity & Security Model

- **Workload Identity Federation**: Pods assume Google Cloud IAM identities without static keys
- **Secret Manager integration**: Secrets synced to Kubernetes with automatic rotation
- **Pod Security Standards**: `restricted` profile enforced on production namespaces
- **Shielded Nodes**: Secure Boot and integrity monitoring (Autopilot-enforced)

## Regional Availability

GKE is available in all Google Cloud regions. Autopilot clusters are regional by default. See https://cloud.google.com/about/locations for the full region list.

## Pricing

GKE pricing depends on the cluster mode:
- **Autopilot**: Pay for pod resource requests (vCPU, memory, ephemeral storage). No cluster management fee.
- **Standard**: Pay for underlying Compute Engine VMs plus a per-cluster management fee.

For current pricing, see https://cloud.google.com/kubernetes-engine/pricing.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall