workload-rebalancing skillA
workload-rebalancing is agent-read markdown (skill) from gke-labs/kube-agents: Orchestrate cross-cluster workload rebalancing using the kanban board with the validation-then-declare pattern. Use when fleet utilization shows one cluster overutilized and another with headroom and a workload should move..
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
# Workload Rebalancing Skill (validation-then-declare) When live cluster utilization — checked via the read-only `gke` MCP / `kubectl top` on each cluster — shows a cluster **overutilized / under pressure** and another with **headroom**, you may relocate a workload. You act as an **orchestrator**: cluster agents _validate_ feasibility (read-only); **you** _declare_ the change as a single GitOps PR; **KCC** reconciles the actual move. Never issue imperative start/stop. ## When to use vs. do-it-yourself Delegating is optional. Use this fan-out when you want per-cluster local validation and a single aggregated decision. For a trivial single-cluster change, act directly. ## The card graph (fan-out validation → decide on your own card) Resolve each cluster's profile name first (`cluster_agent_profile.py name --project … --cluster … --location …`), then: 1. **Card A — can clusterA host it?** `kanban_create(assignee="<clusterA-profile>", title="Validate can-host <workload>", body="Can you host <ns/workload> (needs ~<cpu>/<mem>)? Check capacity, affinity/taints, quotas. Do NOT mutate.")` …
Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/workload-rebalancing@git:20260904.b90acf7mdr add gke-labs/kube-agents/workload-rebalancing@sha256:69da9804ca62e0c9Pin 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_kmoqq23osrfwij3k)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260904.b90acf7 latest | 2026-09-04 | b90acf7 | 3,767 B | A | view · diff |
| git:20260812.8e8a46c | 2026-08-12 | 8e8a46c | 3,700 B | A | view · diff |
| git:20260728.aca5b5c | 2026-07-28 | aca5b5c | 3,398 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 (3767 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_kmoqq23osrfwij3k GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/workload-rebalancing GET https://markdownregistry.com/api/v1/blob/69da9804ca62e0c92e788c5c60b18c15bcd4c67b8ef6d7b9fcff1d147bfd6c44
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.