gke-compute-classes

Configure, optimize, and troubleshoot GKE ComputeClasses for workload scheduling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Configuring GKE ComputeClasses manually is error-prone, with common pitfalls including scheduling conflicts, node stockouts, misaligned cost optimizations, and unenforced access controls that lead to wasted spend or workload downtime. This Skill eliminates those risks by providing validated guidance, guardrails, and pre-built templates for end-to-end ComputeClass management.

Core Features & Use Cases

  • Cost Optimization: Configure Spot VMs with on-demand fallback, align machine families with existing Committed Use Discounts (CUDs) and reservations, and implement priority ladders to minimize spend while maintaining availability.
  • Workload Targeting: Set up ComputeClasses for GPU/TPU workloads, specific machine families (c3, c4, n4), and zonal resource colocation for performance-sensitive applications.
  • Troubleshooting: Diagnose and fix pending pods, scheduling failures, and ComputeClass misconfigurations, including common issues like missing GPU tolerations, reservation affinity errors, and stockout cascades.
  • Governance: Restrict ComputeClass access using RBAC for CRUD operations and ValidatingAdmissionPolicy for consumption control, preventing unauthorized teams from modifying or requesting high-cost classes.
  • Use Case Example: For a team running latency-sensitive AI inference on GKE, use this Skill to build a ComputeClass that prioritizes GPU reservations, falls back to on-demand nodes, and enforces guardrails to avoid Spot preemption for production traffic.

Quick Start

Use the gke-compute-classes skill to generate a validated ComputeClass YAML template for your GPU inference workload that aligns with your existing committed use discounts and includes proper tolerations for GPU nodes.

Frequently Asked Questions about gke-compute-classes

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

FAQPage Schema
How do I configure GKE ComputeClasses for Spot VMs with on-demand fallback?

Configure GKE ComputeClasses for Spot VMs with on-demand fallback by setting up priority ladders in the ComputeClass YAML that prioritize Spot instances and trigger on-demand node creation during stockouts or preemptions. This minimizes spend while maintaining workload availability.

Why are my GKE pods pending when using ComputeClasses for GPU scheduling?

GKE pods pending during GPU scheduling with ComputeClasses often result from missing GPU tolerations, reservation affinity errors, or node pool auto-creation misconfigurations. Diagnose the scheduling failures by validating the ComputeClass schema and checking node pool stockout cascades.

What is the best way to align GKE machine families with Committed Use Discounts?

Align GKE machine families with Committed Use Discounts by selecting specific families like c3, c4, or n4 in your ComputeClass configuration to match existing reservations. This ensures workload targeting respects cost guardrails and maximizes discount utilization.

Can I restrict access to specific GKE ComputeClasses using RBAC?

Restrict access to GKE ComputeClasses using RBAC for CRUD operations and ValidatingAdmissionPolicy for consumption control. This governance prevents unauthorized teams from modifying or requesting high-cost classes, enforcing strict security and cost guardrails.

Does GKE ComputeClass support zonal resource colocation for latency-sensitive applications?

GKE ComputeClass supports zonal resource colocation for latency-sensitive applications by targeting specific machine families and zones within the configuration. This enables performance-sensitive workloads to schedule nodes in the same zone for reduced latency.

How do I troubleshoot ComputeClass misconfigurations causing node pool auto-creation failures?

Troubleshoot ComputeClass misconfigurations causing node pool auto-creation failures by validating the CRD schema compliance and inspecting scheduling constraints like GPU tolerations or reservation affinity errors that block node provisioning. Debug pending pods to isolate the cascade.