kubernetes patterns
- Repo stars 0
- Author repo skills-registry
- Domain
- DevOps
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Kubernetes Patterns
Deploy and manage production Kubernetes clusters.
## Core Objects
### Workloads
| Object | Use Case | Scaling |
|--------|----------|---------|
| Deployment | Stateless apps | Replicas, HPA |
| StatefulSet | Stateful apps (DBs) | Stable network IDs |
| DaemonSet | Per-node agents (logging, monitoring) | Node count |
| Job/CronJob | Batch tasks, scheduled jobs | Completion |
### Networking
- **Service**: Stable endpoint for pods (ClusterIP, NodePort, LoadBalancer)
- **Ingress**: HTTP routing, TLS termination, path-based routing
- **Network Policies**: Pod-level firewall rules
## Production Best Practices
### Resource Management
```yaml
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 500m
memory: 256Mi
```
- Always set requests AND limits
- Use LimitRange for namespace defaults
- Use ResourceQuota for namespace caps
### Pod Anti-Affinity
Spread pods across nodes for HA.
### Readiness & Liveness Probes
- Readiness: traffic starts flowing
- Liveness: pod gets restarted
- Startup: for slow-starting containers
## RBAC
- Least-privilege service accounts per app
- Namespace-scoped roles (not cluster-wide)
- Regularly audit permissions
- Use groups, not individual users
## Autoscaling
- HPA: scale by CPU/memory or custom metrics
- VPA: adjust resource requests automatically
- Cluster Autoscaler: add/remove nodes
- KEDA: event-driven scaling (SQS queue depth, etc.)
---
> Source: [cosmicstack-labs/mercury-agent-skills](https://github.com/cosmicstack-labs/mercury-agent-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
sections -> Core Objects → Workloads → Networking → Production Best Practices → Resource Management → Pod Anti-Affinity
terms -> Service · Ingress · Network Policies · Deploy and manage production Kubernetes clusters.
files/cmd -> Job/CronJob · CPU/memory · add/remove · cosmicstack-labs/mercury-agent-skills · github.com/cosmicstack-labs/mercury-agent-skills
body sha256 -> dee085d8483f
Workloads
Object · Use Case · Scaling Deployment · Stateless apps · Replicas, HPA StatefulSet · Stateful apps (DBs) · Stable network IDs DaemonSet · Per-node agents (logging, monitoring) · Node count Job/CronJob · Batch tasks, scheduled jobs · Completion
Networking
Service: Stable endpoint for pods (ClusterIP, NodePort, LoadBalancer) Ingress: HTTP routing, TLS termination, path-based routing Network Policies: Pod-level firewall rules
Resource Management
Always set requests AND limits Use LimitRange for namespace defaults Use ResourceQuota for namespace caps
Pod Anti-Affinity
Spread pods across nodes for HA.
Readiness & Liveness Probes
Readiness: traffic starts flowing Liveness: pod gets restarted Startup: for slow-starting containers