Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Kubernetes Mistake Avoidance Guidance

ASecurity

Avoid common Kubernetes mistakes — resource limits, probe configuration, selector mismatches, and RBAC pitfalls.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoshellnodeexpresskubernetesdebuggingdevops

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill kubernetes-mistake-avoidance-guidance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Kubernetes Mistake Avoidance Guidance?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Kubernetes Mistake Avoidance Guidance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-kubernetes-mistake-avoidance-guidance/badge)](https://www.skillsdirectory.com/skills/rondoflow-kubernetes-mistake-avoidance-guidance)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: kubernetes-mistake-avoidance-guidance
description: "Avoid common Kubernetes mistakes — resource limits, probe configuration, selector mismatches, and RBAC pitfalls."
category: "DevOps & Infra"
author: community
version: "1.0.0"
icon: server
---

## Resource Management
- `requests` = guaranteed minimum — scheduler uses this for placement
- `limits` = maximum allowed — exceeding memory = OOMKilled, CPU = throttled
- No limits = can consume entire node — always set production limits
- `requests` without `limits` = burstable — can use more if available

## Probes
- `readinessProbe` controls traffic — fails = removed from Service endpoints
- `livenessProbe` restarts container — fails = container killed and restarted
- `startupProbe` for slow starts — disables liveness/readiness until success
- Don't use same endpoint for liveness and readiness — liveness should be minimal health check

## Probe Pitfalls
- Liveness probe checking dependencies — if DB down, all pods restart indefinitely
- `initialDelaySeconds` too short — pod killed before app starts
- `timeoutSeconds` too short — slow response = restart loop
- HTTP probe to HTTPS endpoint — needs `scheme: HTTPS`

## Labels and Selectors
- Service selector must match Pod labels exactly — typo = no endpoints
- Deployment selector is immutable — can't change after creation
- Use consistent labeling scheme — `app`, `version`, `environment`
- `matchExpressions` for complex selection — `In`, `NotIn`, `Exists`

## ConfigMaps and Secrets
- ConfigMap changes don't restart pods — mount as volume for auto-update, or restart manually
- Secrets are base64 encoded, not encrypted — use external secrets manager for sensitive data
- `envFrom` imports all keys — `env.valueFrom` for specific keys
- Volume mount makes files — `subPath` for single file without replacing directory

## Networking
- `ClusterIP` internal only — default, only accessible within cluster
- `NodePort` exposes on node IP — 30000-32767 range, not for production
- `LoadBalancer` provisions cloud LB — works only in supported environments
- Ingress needs Ingress Controller — nginx-ingress, traefik, etc. installed separately

## Persistent Storage
- PVC binds to PV — must match capacity and access modes
- `storageClassName` must match — or use `""` for no dynamic provisioning
- `ReadWriteOnce` = single node — `ReadWriteMany` needed for multi-pod
- Pod deletion doesn't delete PVC — `persistentVolumeReclaimPolicy` controls PV fate

## Common Mistakes
- `kubectl apply` vs `create` — apply for declarative (can update), create for imperative (fails if exists)
- Forgetting namespace — `-n namespace` or set context default
- Image tag `latest` in production — no version pinning, unpredictable updates
- Not setting `imagePullPolicy` — `Always` for latest tag, `IfNotPresent` for versioned
- Service port vs targetPort — port is Service's, targetPort is container's

## Debugging
- `kubectl describe pod` for events — shows scheduling failures, probe failures
- `kubectl logs -f pod` for logs — `-p` for previous container (after crash)
- `kubectl exec -it pod -- sh` for shell — debug inside container
- `kubectl get events --sort-by=.lastTimestamp` — cluster-wide events timeline

## RBAC
- `ServiceAccount` per workload — not default, for least privilege
- `Role` is namespaced — `ClusterRole` is cluster-wide
- `RoleBinding` binds Role to user/SA — `ClusterRoleBinding` for cluster-wide
- Check permissions: `kubectl auth can-i verb resource --as=system:serviceaccount:ns:sa`

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →