k8s-autoscaling

Configure HPA, VPA, and KEDA autoscaling for Kubernetes deployments.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/zangxin75/openclaw-skills --skill k8s-autoscaling-zangxin75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-autoscaling
Source: https://github.com/zangxin75/openclaw-skills/tree/main/k8-autoscaling
Command: npx skills add https://github.com/zangxin75/openclaw-skills --skill k8s-autoscaling-zangxin75

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex task of configuring and managing autoscaling in Kubernetes environments, ensuring optimal resource utilization and application performance.

Core Features & Use Cases

  • Horizontal Pod Autoscaling (HPA): Automatically adjust the number of pod replicas based on CPU or memory utilization.
  • Vertical Pod Autoscaling (VPA): Dynamically adjust resource requests and limits for containers.
  • KEDA (Event-Driven Autoscaling): Scale applications based on external event sources like message queues or custom metrics.
  • Use Case: You have a web application experiencing unpredictable traffic spikes. Use this Skill to configure HPA to scale out during peak hours and KEDA with a Prometheus trigger to scale based on request latency, ensuring a smooth user experience and cost efficiency.

Quick Start

Use the k8s-autoscaling skill to apply a Horizontal Pod Autoscaler configuration for the 'my-app' deployment in the 'default' namespace.

Frequently Asked Questions about k8s-autoscaling

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

FAQPage Schema
How do I configure Kubernetes autoscaling for a deployment with unpredictable traffic spikes?

You can configure Kubernetes autoscaling by applying Horizontal Pod Autoscaler (HPA) to automatically adjust pod replicas based on CPU or memory utilization, or use KEDA to scale based on external event sources like Prometheus request latency metrics.

When do I need Vertical Pod Autoscaling instead of Horizontal Pod Autoscaling?

You need Vertical Pod Autoscaling (VPA) when you want to dynamically adjust CPU and memory resource requests and limits for containers, whereas Horizontal Pod Autoscaling (HPA) adjusts the number of pod replicas instead of resource allocations.

Can I scale my Kubernetes applications to zero based on custom metrics?

Yes, you can scale Kubernetes applications to zero by configuring KEDA for event-driven autoscaling, which uses external event sources like message queues or custom metrics to enable scale-to-zero capabilities for cost optimization.

What's the best way to scale Kubernetes pods based on message queue events?

The best way to scale Kubernetes pods based on message queue events is configuring KEDA for event-driven autoscaling, which dynamically adjusts pod replicas in response to external event source metrics for optimal resource utilization.

Does this Kubernetes autoscaling approach work with kubectl-mcp-server tools?

Yes, this Kubernetes autoscaling approach integrates directly with kubectl-mcp-server tools to execute operational tasks, allowing you to apply and manage HPA, VPA, and KEDA configurations seamlessly within your existing environment.