
Gke workload scaling troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as <unknown>, FailedGetResourceMetric / FailedGetScale / FailedComput
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 24.4K
- Last commit
- today
- License
- Apache-2.0
- Listing updated
- today
When your agent uses it
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as <unknown>, FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter, control-plane firewall blocking the adapter), HPA that won't scale up or down (tolerance / stabilization window / unavailable rate metrics), scale-to/from-zero problems, and slow HPA reaction on large clusters. Use when an HPA isn't scaling a workload as expected or reports metric errors. Don't use for configuring or authoring new HPA/VPA objects or scaling best practices (see the gke-workload-scaling skill), or for Cluster Autoscaler / node-pool sizing.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 2 files (19 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Install
Copy the skill folder to ~/.claude/skills/gke-workload-scaling-troubleshooting to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/gke-workload-scaling-troubleshooting &&
cp -R "$tmp/skills/cloud/gke-workload-scaling-troubleshooting" ~/.claude/skills/gke-workload-scaling-troubleshooting &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/gke-workload-scaling-troubleshooting inside it instead.
Copy the skill folder to ~/.agents/skills/gke-workload-scaling-troubleshooting to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/gke-workload-scaling-troubleshooting &&
cp -R "$tmp/skills/cloud/gke-workload-scaling-troubleshooting" ~/.agents/skills/gke-workload-scaling-troubleshooting &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/gke-workload-scaling-troubleshooting inside it instead.
Copy the skill folder to ~/.cursor/skills/gke-workload-scaling-troubleshooting to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/gke-workload-scaling-troubleshooting &&
cp -R "$tmp/skills/cloud/gke-workload-scaling-troubleshooting" ~/.cursor/skills/gke-workload-scaling-troubleshooting &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/gke-workload-scaling-troubleshooting inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/google/skills.git --path skills/cloud/gke-workload-scaling-troubleshootingOr copy the folder to ~/.gemini/skills/gke-workload-scaling-troubleshooting yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/gke-workload-scaling-troubleshooting:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/gke-workload-scaling-troubleshooting &&
cp -R "$tmp/skills/cloud/gke-workload-scaling-troubleshooting" ~/.copilot/skills/gke-workload-scaling-troubleshooting &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/gke-workload-scaling-troubleshooting inside it instead.
Get the folder:
git clone --depth 1 https://github.com/google/skills.gitThen copy skills/skills/cloud/gke-workload-scaling-troubleshooting into your agent's skills folder as gke-workload-scaling-troubleshooting. Agents that support SKILL.md read one folder per skill.
Gke workload scaling troubleshooting FAQ
How do I install Gke workload scaling troubleshooting in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/gke-workload-scaling-troubleshooting to use it in all your projects, or to .claude/skills/gke-workload-scaling-troubleshooting in one project.
Does Gke workload scaling troubleshooting run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Gke workload scaling troubleshooting?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
More from google/skills

Google platform decision and setup guidance, loaded on demand from Google's skill catalog
- Open source
- 24.4K GitHub stars

Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services an
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Provides expert guidance on Identity and Access Management (IAM) and authenticating and authorizing to Google Cloud services and APIs, cover
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resour
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter,
- Open source
- 24.4K GitHub stars

Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its
- Open source
- 24.4K GitHub stars