Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
k8s-scaling-availability - Skill - OpenSmartRoute
Skillv1.0.0
k8s-scaling-availability
See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01
Imported from faionfaion/faion-network (skills/faion/knowledge/infra/k8s-scaling-availability/AGENTS.md). Install upstream with npx skills add faionfaion/faion-network --skill k8s-scaling-availability. Copyright stays with the author.
Kubernetes Scaling and Availability
Summary
One-sentence: Scaling + availability spec (config): HorizontalPodAutoscaler v2, topology-spread, anti-affinity, PDB, multi-AZ node-pool target - produced as deployment-extension manifest.
One-paragraph: Scaling + availability spec (config): HorizontalPodAutoscaler v2, topology-spread, anti-affinity, PDB, multi-AZ node-pool target - produced as deployment-extension manifest. The methodology pins the discipline that turns folklore into a reviewable, owned, version-controlled operating artefact: rule-bound output contract, evidence anchors, named owner, published review cadence. Outputs of the wrong shape are rejected at review; outputs without evidence are demoted to hypotheses; outputs without owners are tagged stale.
Applies If (ALL must hold)
Adding HorizontalPodAutoscaler v2 to a service.
Spreading pods across availability zones / nodes.
Tightening PDB to survive node-pool upgrades.
Recovering from co-located outages (all pods on one node).
Skip If (ANY kills it)
Workload with stable, predictable load - fixed replicas may be cheaper.
Step-by-step procedure to apply the methodology end-to-end
800
content/06-decision-tree.xml
essential
Routing tree on observable signals -> rule from 01-core-rules.xml
600
Task Routing
Sub-task
Model
Rationale
scaffold-config
haiku
Mechanical template fill from prerequisites table.
populate-policy
sonnet
Per-clause translation into config fields with judgment.
review-breach-cases
opus
Cross-engagement risk + failure-mode synthesis.
Templates
File
Purpose
templates/config.json
Config skeleton matching the output schema.
templates/_smoke-test.json
Minimum viable filled artefact.
Scripts
File
Purpose
When to call
scripts/validate-k8s-scaling-availability.py
Validate artefact against the JSON Schema in content/02-output-contract.xml. Stdlib-only.
CI on artefact change; pre-commit.
Related
[[k8s-rolling-update]]
[[k8s-resource-requests-limits]]
Decision tree
See content/06-decision-tree.xml. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from 01-core-rules.xml. Use it when in doubt about which variant of the methodology to apply.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/faionfaion-faion-network-k8s-scaling-availability/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "faionfaion-faion-network-k8s-scaling-availability",
"kind": "skill",
"name": "k8s-scaling-availability",
"description": "See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01-core-rules.xml`. Use it when in doubt about which variant of the methodology to apply.",
"publisher": "faionfaion",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01-core-rules.xml`. Use it when in doubt about which variant of the methodology to apply."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/faionfaion/faion-network",
"path": "skills/faion/knowledge/infra/k8s-scaling-availability/AGENTS.md",
"ref": "8e31684537e64d45c75264b1e0a2384f9b024a34",
"url": "https://github.com/faionfaion/faion-network/blob/8e31684537e64d45c75264b1e0a2384f9b024a34/skills/faion/knowledge/infra/k8s-scaling-availability/AGENTS.md",
"key": "faionfaion/faion-network/skills/faion/knowledge/infra/k8s-scaling-availability/AGENTS.md"
}
},
"instructions": "# Kubernetes Scaling and Availability\n\n## Summary\n\n**One-sentence:** Scaling + availability spec (config): HorizontalPodAutoscaler v2, topology-spread, anti-affinity, PDB, multi-AZ node-pool target - produced as deployment-extension manifest.\n\n**One-paragraph:** Scaling + availability spec (config): HorizontalPodAutoscaler v2, topology-spread, anti-affinity, PDB, multi-AZ node-pool target - produced as deployment-extension manifest. The methodology pins the discipline that turns folklore into a reviewable, owned, version-controlled operating artefact: rule-bound output contract, evidence ancho",
"cost": {
"context_tokens": 988
}
}
Fetch it by URL: GET /api/v1/registry/faionfaion-faion-network-k8s-scaling-availability/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
