gke-workload-scaling skillA
gke-workload-scaling is agent-read markdown (skill) from gke-labs/kube-agents: Manages scaling for GKE workloads using HPA and VPA. Use when configuring Horizontal Pod Autoscaler (HPA), configuring Vertical Pod Autoscaler (VPA), or applying best practices for GKE workload autoscaling. Do not use for cluster-level autoscaling (Cluster Autoscaler), static cluster sizing, or configuring node-level machine styles directly..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GKE Workload Scaling
This skill provides workflows and best practices for scaling applications on
Google Kubernetes Engine (GKE). It covers manual scaling, Horizontal Pod
Autoscaling (HPA), and Vertical Pod Autoscaling (VPA).
## Workflows
### 1. Manual Scaling
Scale a deployment to a fixed number of replicas. Useful for immediate manual
intervention or testing.
**Command:**
```bash
kubectl scale deployment {deployment_name} --replicas={number} -n {namespace}
# Verify the scale event
kubectl get deployment {deployment_name} -n {namespace}
```
### 2. Horizontal Pod Autoscaling (HPA)
Automatically scale the number of pods based on observed CPU utilization, memory
utilization, or custom metrics.
**Prerequisites:**
- Metrics Server must be running (enabled by default on GKE).
- Containers clearly define resource requests/limits.
**Quick Command:**
```bash
kubectl autoscale deployment {deployment_name} --cpu-percent=50 --min=1 --max=10
```
**Manifest Approach (Recommended):** Use a YAML manifest for version-controlled
configuration. See [assets/hpa-example.yaml](assets/hpa-example.yaml) for a
template.
```bash
kubectl apply -f assets/hpa-example.yaml
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-workload-scaling@git:20260807.d47bdf1mdr add gke-labs/kube-agents/gke-workload-scaling@sha256:cca5bf26a2d77628Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ohc3owisxzdnzugs)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260807.d47bdf1 latest | 2026-08-07 | d47bdf1 | 4,994 B | A | view · diff |
| git:20260710.9319bce | 2026-07-10 | 9319bce | 3,975 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4994 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gke-labs/kube-agents · 64 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ohc3owisxzdnzugs GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-workload-scaling GET https://markdownregistry.com/api/v1/blob/cca5bf26a2d776283ae871f52bafe60e84d3bdf200c6aa9260a1ae4fe27cbcdf
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from gke-labs/kube-agents
Every file in gke-labs/kube-agents