gke-scaling

Configure GKE autoscaling with HPA, VPA, and Node Auto-Provisioning.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill gke-scaling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-scaling
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/cloud/gke-scaling
Command: npx skills add https://github.com/wangx7/skills-collection --skill gke-scaling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Manually configuring GKE autoscaling mechanisms is complex, time-consuming, and error-prone, often leading to suboptimal resource utilization, unexpected scaling behavior, or unnecessary cloud costs for teams managing containerized workloads.

Core Features & Use Cases

  • Multi-mechanism autoscaling support: Guides configuration of Horizontal Pod Autoscaling (HPA) for pod count scaling, Vertical Pod Autoscaling (VPA) for pod resource request optimization, and Node Auto-Provisioning (NAP) for dynamic node pool scaling.
  • Validated golden path defaults: Provides pre-tested, cost-optimized default settings including the OPTIMIZE_UTILIZATION autoscaling profile and enabled VPA/NAP for rapid, reliable production deployment.
  • Real-world use case: A DevOps engineer can use this skill to implement production-grade autoscaling for a GKE-hosted microservice in minutes, avoiding manual configuration of multiple Kubernetes manifests and gcloud CLI commands.

Quick Start

Use the gke-scaling skill to configure recommended autoscaling defaults for your GKE cluster including VPA, NAP, and the OPTIMIZE_UTILIZATION profile.

Frequently Asked Questions about gke-scaling

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

FAQPage Schema
How do I configure GKE autoscaling for HPA, VPA, and Node Auto-Provisioning?

Configure GKE autoscaling by applying validated production-ready manifests for Horizontal Pod Autoscaling, Vertical Pod Autoscaling, and Node Auto-Provisioning to eliminate manual configuration errors and optimize cluster resources.

What is the best way to reduce cloud costs for containerized workloads in GKE?

Reduce GKE cloud costs by implementing the OPTIMIZE_UTILIZATION autoscaling profile alongside VPA and NAP to dynamically rightsize pod resource requests and automatically scale node pools based on actual workload demand.

Does GKE Node Auto-Provisioning work with Vertical Pod Autoscaling?

Yes, GKE Node Auto-Provisioning works with Vertical Pod Autoscaling. Combining NAP for dynamic node pool scaling and VPA for pod resource optimization provides a complete multi-mechanism autoscaling strategy aligned with GKE operational standards.

How does VPA rightsizing improve Kubernetes workload resource optimization?

VPA rightsizing improves workload optimization by automatically analyzing historical container resource usage and adjusting CPU and memory requests, which prevents resource starvation and eliminates unnecessary cloud cost overhead from over-provisioned pods.

What are the limitations of manually configuring Horizontal Pod Autoscaling in GKE?

Manually configuring Horizontal Pod Autoscaling is complex and error-prone, often leading to suboptimal resource utilization, unexpected pod count scaling behavior, and unnecessary cloud costs without validated golden path defaults and best practice guardrails.

When do I need to enable the OPTIMIZE_UTILIZATION autoscaling profile for GKE?

Enable the OPTIMIZE_UTILIZATION autoscaling profile for GKE when you need rapid, reliable production deployment with cost-optimized default settings for dynamically managing microservice resource allocation across your cluster.