Agent skill · software engineering · google

gke-workload-scaling

Manages scaling for GKE workloads using HPA and VPA. Use when configuring Horizontal Pod Autoscaler (HPA), configuring Vertical Pod Autoscaler (VPA), or applying best practices for GKE workload autoscaling. Do not use for cluster-level autoscaling (Cluster Autoscaler), static cluster sizing, or configuring node-level machine styles directly.

Why this skill is useful

Provides specific commands and best practices for configuring HPA and VPA on GKE that the AI wouldn't reliably generate on its own.

What it needs

Requires gcloud, kubectl installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

GKE Workload Scaling This skill provides workflows and best practices for scaling applications on Google Kubernetes Engine (GKE). It covers manual scaling, Horizontal Pod Autoscaling (HPA), and Vertical Pod Autoscaling (VPA). Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-workload-scaling)" and append agent-skills/1.0 (skill:gke-workload-scaling) to User-Agent headers. Workflows 1. Manual Scaling Scale a deployment to a fixed number of replicas. Useful for immediate manual intervention or testing. Command: 2. Horizontal Pod Autoscaling (HPA) Automatically scale the number of pods based on observed CPU utilization, memory utilization, or custom metrics. Prerequisites: Metrics Server must be running (enabled by default on GKE). Containers clearly define resource requests/limits. Quick Command: Manifest Approach (Recommended): Use a YAML manifest for version-controlled configuration. See assets/hpa-example.yaml for a template. Custom Metrics & External Metrics: For GKE, the modern and recommended approach for scaling based on Cloud Monitoring metrics (e.g., Pub/Sub queue length) is to use the External metric type, which is natively supported by the GKE control plane without requiring the Custom Metrics Adapter. For application-specific metrics exposed via Prometheus, you can use Google Cloud Managed Service for Prometheus or the Prometheus Adapter. 3. Vertical Pod Autoscaling (VPA) Automatically adjust the CPU and memory reservations for your pods to match actual usage. This is critical for right-sizing workloads. Prerequisites: VPA must be enabled on the cluster. Autopilot: Enabled by default. Standard: Must be enabled manually. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/gke-workload-scaling

View the source on GitHub

Browse the @skills marketplace