Claude Cursor Skill

k8s-manifest-generator

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.

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_kubernetes-operations_skills_k8s-manifest-generator-7e2fb55.zip · 19 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/kubernetes-operations/skills/k8s-manifest-generator
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

  1. Always set resource requests and limits - Prevents resource starvation
  2. Implement health checks - Ensures Kubernetes can manage your application
  3. Use specific image tags - Avoid unpredictable deployments
  4. Apply security contexts - Run as non-root, drop capabilities
  5. Use ConfigMaps and Secrets - Separate config from code
  6. Label everything - Enables filtering and organization
  7. Follow naming conventions - Use standard Kubernetes labels
  8. Validate before applying - Use dry-run and validation tools
  9. Version your manifests - Keep in Git with version control
  10. 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:

  1. Store in Git repository
  2. Set up CI/CD pipeline for deployment
  3. Consider using Helm or Kustomize for templating
  4. Implement GitOps with ArgoCD or Flux
  5. Add monitoring and observability

Related Skills

  • helm-chart-scaffolding - For templating and packaging
  • gitops-workflow - For automated deployments
  • k8s-security-policies - For advanced security configurations
Files (agents)
  • assets
    • configmap-template.yaml 6.1 KB
      Loading…
    • deployment-template.yaml 5.1 KB
      Loading…
    • service-template.yaml 3.6 KB
      Loading…
  • references
    • deployment-spec.md 17.3 KB
      Loading…
    • details.md 10.6 KB
      Loading…
    • service-spec.md 13.8 KB
      Loading…
  • SKILL.md 3 KB
    ---
    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
    
    1. **Always set resource requests and limits** - Prevents resource starvation
    2. **Implement health checks** - Ensures Kubernetes can manage your application
    3. **Use specific image tags** - Avoid unpredictable deployments
    4. **Apply security contexts** - Run as non-root, drop capabilities
    5. **Use ConfigMaps and Secrets** - Separate config from code
    6. **Label everything** - Enables filtering and organization
    7. **Follow naming conventions** - Use standard Kubernetes labels
    8. **Validate before applying** - Use dry-run and validation tools
    9. **Version your manifests** - Keep in Git with version control
    10. **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:
    
    1. Store in Git repository
    2. Set up CI/CD pipeline for deployment
    3. Consider using Helm or Kustomize for templating
    4. Implement GitOps with ArgoCD or Flux
    5. Add monitoring and observability
    
    ## Related Skills
    
    - `helm-chart-scaffolding` - For templating and packaging
    - `gitops-workflow` - For automated deployments
    - `k8s-security-policies` - For advanced security configurations
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.