gke-scaling

Automate GKE workload scaling with HPA, VPA, and Node Auto Provisioning.

17.1k|1.4k|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/google/skills --skill gke-scaling-google
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-scaling
Source: https://github.com/google/skills/tree/main/skills/cloud/gke-scaling
Command: npx skills add https://github.com/google/skills --skill gke-scaling-google

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the complexities of managing and optimizing GKE scaling, ensuring your workloads are efficiently sized to meet demand while keeping costs in check.

Core Features & Use Cases

  • HPA Setup: Automates the creation and configuration of Horizontal Pod Autoscalers for dynamic scaling based on CPU and memory usage.
  • VPA Configuration: Sets up and manages Vertical Pod Autoscalers to adjust pod resources in response to usage patterns.
  • NAP Management: Facilitates Node Auto Provisioning to automatically add or remove nodes in a GKE cluster.
  • Use Case: Ideal for GKE administrators who need to scale their GKE workloads dynamically, save on costs, and maintain optimal resource allocation.

Quick Start

Use the gke-scaling skill to enable Horizontal Pod Autoscaling on the 'my-gke-cluster' deployment based on CPU utilization.

Frequently Asked Questions about gke-scaling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GKE scaling based on CPU and memory usage?

Automate GKE scaling by configuring Horizontal Pod Autoscalers (HPA) to dynamically adjust pod counts based on real-time CPU and memory utilization. This Skill handles HPA setup to ensure your workloads scale efficiently to meet demand.

What is the difference between HPA and VPA for GKE workload scaling?

HPA scales GKE workloads horizontally by adding or removing pods based on CPU and memory usage, while VPA adjusts resource requests and limits vertically for existing pods. This Skill manages both to optimize resource allocation and costs.

Do I need kubectl to manage Node Auto Provisioning in GKE?

Yes, you need kubectl and GKE configuration access to manage Node Auto Provisioning (NAP). NAP automatically adds or removes nodes in your cluster, and this Skill requires kubectl to facilitate that cluster management.

When should I use Vertical Pod Autoscaler configuration on my GKE cluster?

Use VPA configuration on your GKE cluster when you need to adjust pod resources in response to changing usage patterns. This Skill sets up VPA to maintain optimal resource allocation for dynamic workloads, preventing over-provisioning.

Can I optimize GKE deployment costs by automating cluster scaling?

Yes, you can optimize GKE deployment costs by automating cluster scaling. This Skill manages HPA, VPA, and NAP to dynamically size workloads and nodes, ensuring efficient resource utilization and keeping operational costs in check.

What is the best way to dynamically scale GKE deployments for dynamic traffic?

The best way to dynamically scale GKE deployments is by combining HPA for pod-level scaling and NAP for node-level provisioning. This Skill automates both to handle traffic spikes while maintaining optimal resource allocation.