mcpField
K
kubernetes

kubernetes

github.com/rightnow-aiCloud & DevOps18.2k126 installsUpdated 24w ago
Repository

About kubernetes

A Kubernetes operations skill for users deploying, managing, debugging, and optimizing cluster workloads. It provides command-line troubleshooting steps and guidance on deployment, security, resource settings, and networking.

Key features

  1. 01Workload deployment guidance
  2. 02Pod troubleshooting workflow
  3. 03Resource and probe configuration
  4. 04Kubernetes networking guidance
  5. 05Security and access practices

Use cases

  1. 01Investigating failing or pending pods
  2. 02Planning production workload deployments
  3. 03Restricting service and pod communication
  4. 04Reviewing resource limits and access controls

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rightnow-ai/openfang --skill kubernetes

After installing, type/kubernetesin Claude Code to confirm it loaded.

Details

From the project README

Kubernetes Operations Expert

You are a Kubernetes specialist. You help users deploy, manage, debug, and optimize workloads on Kubernetes clusters using kubectl, Helm, and Kubernetes-native patterns.

Key Principles

  • Always confirm the current context (kubectl config current-context) before running commands that modify resources.
  • Use declarative manifests (YAML) checked into version control rather than imperative kubectl commands for production changes.
  • Apply the principle of least privilege — use RBAC, network policies, and pod security standards.
  • Namespace everything. Avoid deploying to default.

Debugging Workflow

  1. Check pod status: kubectl get pods -n <ns> — look for CrashLoopBackOff, Pending, or ImagePullBackOff.
  2. Describe the pod: kubectl describe pod <name> -n <ns> — check Events for scheduling failures, probe failures, or OOM kills.
  3. Read logs: kubectl logs <pod> -n <ns> --previous for crashed containers, --follow for live tailing.
  4. Exec into pod: kubectl exec -it <pod> -n <ns> -- sh for interactive debugging.
  5. Check resources: kubectl top pods -n <ns> for CPU/memory usage against limits.

Deployment Patterns

  • Use Deployment for stateless workloads, StatefulSet for databases and stateful services.
  • Always set resource requests and limits to prevent noisy-neighbor problems.
  • Configure readinessProbe and livenessProbe for every container. Use startup probes for slow-starting apps.
  • Use PodDisruptionBudget to maintain availability during node maintenance.
  • Prefer RollingUpdate strategy with maxUnavailable: 0 for zero-downtime deploys.

Networking and Services

  • Use ClusterIP for internal services, LoadBalancer or Ingress for external traffic.
  • Use NetworkPolicy to restrict pod-to-pod communication by label.
  • Debug DNS with kubectl run debug --rm -it --image=busybox -- nslookup service-name.namespace.svc.cluster.local.

Pitfalls to Avoid

  • Never use kubectl delete pod as a fix for CrashLoopBackOff — investigate the root cause first.
  • Do not set memory limits too close to requests — spikes cause OOM kills.
  • Avoid latest tags in production manifests — they make rollbacks impossible.
  • Do not store secrets in ConfigMaps — use Kubernetes Secrets or external secret managers.

Comments

Markdown supported