What problem does it solve? When a GKE HorizontalPodAutoscaler (HPA) stops scaling workloads or reports metric errors like <unknown> values and FailedGet* events, debugging requires deep knowledge of the metrics pipeline, Pod resource requests, and HPA configuration—work that is time-consuming and error-prone. This Skill systematically diagnoses the root cause and guides you to the fix. ## Core Features & Use Cases - HPA Metric Diagnosis: Identifies whether failures stem from missing Pod resource requests, broken custom/external metrics adapters, or invalid HPA configuration. - Metrics Pipeline Validation: Tests connectivity from the HPA controller through the metrics API to Cloud Monitoring, exposing control-plane firewall blocks or adapter crashes. - Scale-to-Zero Troubleshooting: Resolves issues preventing workloads from scaling to or from zero replicas on GKE 1.37+. - Use Case: Your deployment won't scale up despite high CPU usage. The HPA shows ScalingActive: False with reason FailedGetResourceMetric. This Skill guides you through checking Pod resource requests, verifying the metrics server, and confirms the exact manifest correction needed. ## Quick Start Describe the HPA error you're seeing (for example, metrics show unknown, won't scale up, or FailedGetScale events), the cluster name, and the workload namespace, and this Skill will provide step-by-step diagnostics and a corrected HPA or workload manifest to review.