kubernetes-specialist

Generate and validate Kubernetes manifests, Helm charts, RBAC policies, and NetworkPolicies for workload deployment.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lrstanley/skills --skill kubernetes-specialist-lrstanley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubernetes-specialist
Source: https://github.com/lrstanley/skills/tree/main/kubernetes-specialist
Command: npx skills add https://github.com/lrstanley/skills --skill kubernetes-specialist-lrstanley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying and managing Kubernetes workloads involves complex YAML manifests, security hardening, and troubleshooting that are error-prone when done manually. This Skill provides structured guidance and production-grade patterns for the full Kubernetes lifecycle. ## Core Features & Use Cases - Manifest Generation: Create Deployments, StatefulSets, Services, Ingress, ConfigMaps, and Secrets with resource limits, probes, and security contexts built in. - Security Hardening: Apply least-privilege RBAC, default-deny NetworkPolicies, Pod Security Standards, and secret management patterns (Sealed Secrets, External Secrets, SOPS). - Ecosystem Coverage: Get guidance on Helm charts, custom operators (CRDs, controller-runtime), service mesh (Istio/Linkerd), GitOps (ArgoCD/Flux), cost optimization (VPA/HPA, spot instances), and multi-cluster management. - Use Case: You need to deploy a new microservice to production. The Skill produces a complete Deployment manifest with resource limits, liveness/readiness probes, a dedicated ServiceAccount with minimal RBAC, and a NetworkPolicy restricting traffic to only allowed sources. ## Quick Start Ask the agent to create a production-ready Kubernetes Deployment manifest for your application with resource limits, health probes, and a restrictive NetworkPolicy.

Frequently Asked Questions about kubernetes-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a production-ready Kubernetes Deployment manifest?▼

A production Deployment needs resource requests and limits, liveness and readiness probes, a dedicated ServiceAccount, and a security context with runAsNonRoot and readOnlyRootFilesystem. Pin image tags instead of using latest, and validate with kubectl rollout status after applying.

How do I set up NetworkPolicies for network isolation in Kubernetes?▼

Start with a default-deny NetworkPolicy covering all ingress and egress in the namespace, then add explicit allow rules using podSelector and namespaceSelector for required traffic. Remember to allow DNS egress to kube-system on UDP port 53.

ArgoCD vs Flux for GitOps, which should I use?▼

ArgoCD provides a built-in web UI, AppProject multi-tenancy, and centralized architecture, while Flux is distributed, uses native Kubernetes RBAC, and has built-in image update automation. Both support Helm, Kustomize, and progressive delivery with Flagger.

How do I debug a pod that keeps crashing in Kubernetes?▼

Run kubectl describe pod to inspect events and probe failures, then use kubectl logs with the --previous flag to see output from the crashed container. Check that resource limits are not causing OOMKills with kubectl top pods.

How do I manage secrets in Kubernetes without hardcoding credentials?▼

Store sensitive data in Secret resources rather than ConfigMaps or environment literals, and mount them as files with restrictive permissions like 0400. For GitOps workflows, use Sealed Secrets, SOPS with age encryption, or the External Secrets Operator backed by a cloud secret manager.

How do I right-size Kubernetes workloads to reduce costs?▼

Compare actual usage from kubectl top pods against configured requests, then set requests to average usage plus a 10-20 percent buffer. Deploy the Vertical Pod Autoscaler in recommendation mode, tune HPA stabilization windows, and use spot instances with PodDisruptionBudgets for fault-tolerant workloads.