k8s-manifest-generator
wshobson/agents
Generate production-ready Kubernetes manifests with built-in best practices and security standards.
What is k8s-manifest-generator?
Creates well-structured Kubernetes YAML manifests for Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims following cloud-native best practices. Use this when you need to generate K8s resources that are secure, properly configured, and ready for production environments.
- Generate Deployment manifests with resource requests, limits, and health checks
- Create Service resources for network connectivity and load balancing
- Define ConfigMap and Secret resources for configuration management
- Create PersistentVolumeClaim manifests for stateful workloads
- Apply security contexts and non-root user configurations
- Implement proper labeling and naming conventions for resource organization
How to install k8s-manifest-generator
npx skills add https://github.com/wshobson/agents --skill k8s-manifest-generatorHow to use k8s-manifest-generator
- 1.Specify the Kubernetes resource type you need (Deployment, Service, ConfigMap, Secret, or PersistentVolumeClaim)
- 2.Provide application details including image, ports, environment variables, and resource requirements
- 3.Define health checks (liveness and readiness probes) for pod management
- 4.Configure security context settings (non-root user, dropped capabilities)
- 5.Review generated manifests against the best practices checklist
- 6.Validate manifests using kubectl dry-run before applying to cluster
- 7.Store manifests in Git version control for tracking and CI/CD integration
Use cases
- Creating new microservice deployments with proper resource constraints and health checks
- Setting up multi-environment Kubernetes configurations with ConfigMaps and Secrets
- Generating manifests for stateful applications requiring persistent storage
- Implementing security best practices like non-root containers and capability dropping
- Organizing and labeling resources for filtering and multi-tenant cluster management
- DevOps engineers building Kubernetes infrastructure
- Backend developers deploying applications to K8s clusters
- Platform engineers standardizing manifest generation across teams
- SREs implementing production-grade configurations
k8s-manifest-generator FAQ
Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims. For more complex scenarios, consider using Helm or Kustomize templating.
Yes, it enforces setting resource requests and limits as a best practice to prevent resource starvation and ensure proper cluster scheduling.
Use kubectl describe pod <pod-name> to check image pull errors, verify resource availability with kubectl get nodes, and review events with kubectl get events --sort-by='.lastTimestamp'.
Yes, always use specific image tags instead of 'latest' to ensure predictable and reproducible deployments.
Store them in Git, validate with kubectl dry-run, set up a CI/CD pipeline, and consider GitOps tools like ArgoCD or Flux for automated deployments.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
name: k8s-manifest-generator description: Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
Kubernetes Manifest Generator
Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.
Purpose
This skill provides comprehensive guidance for generating well-structured, secure, and production-ready Kubernetes manifests following cloud-native best practices and Kubernetes conventions.
When to Use This Skill
Use this skill when you need to:
- Create new Kubernetes Deployment manifests
- Define Service resources for network connectivity
- Generate ConfigMap and Secret resources for configuration management
- Create PersistentVolumeClaim manifests for stateful workloads
- Follow Kubernetes best practices and naming conventions
- Implement resource limits, health checks, and security contexts
- Design manifests for multi-environment deployments
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices Summary
- Always set resource requests and limits - Prevents resource starvation
- Implement health checks - Ensures Kubernetes can manage your application
- Use specific image tags - Avoid unpredictable deployments
- Apply security contexts - Run as non-root, drop capabilities
- Use ConfigMaps and Secrets - Separate config from code
- Label everything - Enables filtering and organization
- Follow naming conventions - Use standard Kubernetes labels
- Validate before applying - Use dry-run and validation tools
- Version your manifests - Keep in Git with version control
- Document with annotations - Add context for other developers
Troubleshooting
Pods not starting:
- Check image pull errors:
kubectl describe pod <pod-name> - Verify resource availability:
kubectl get nodes - Check events:
kubectl get events --sort-by='.lastTimestamp'
Service not accessible:
- Verify selector matches pod labels:
kubectl get endpoints <service-name> - Check service type and port configuration
- Test from within cluster:
kubectl run debug --rm -it --image=busybox -- sh
ConfigMap/Secret not loading:
- Verify names match in Deployment
- Check namespace
- Ensure resources exist:
kubectl get configmap,secret
Next Steps
After creating manifests:
- Store in Git repository
- Set up CI/CD pipeline for deployment
- Consider using Helm or Kustomize for templating
- Implement GitOps with ArgoCD or Flux
- Add monitoring and observability
Related Skills
helm-chart-scaffolding- For templating and packaginggitops-workflow- For automated deploymentsk8s-security-policies- For advanced security configurations
Related skills
More from wshobson/agents and the wider catalog.
k8s-security-policies
Implement NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards for production Kubernetes security.
kpi-dashboard-design
Design executive KPI dashboards with metrics selection, visualization patterns, and real-time monitoring best practices.
langchain-architecture
Design LLM applications with LangChain 1.x and LangGraph for agents, memory, and tool integration.
linkerd-patterns
Lightweight, security-first service mesh patterns for Kubernetes with automatic mTLS and traffic control.
llm-evaluation
Comprehensive evaluation framework for LLM applications using automated metrics, human feedback, and benchmarking.
lora-qlora-recipes
Configure LoRA and QLoRA fine-tuning with current best-practice hyperparameters and module targeting.