k8s-yaml-generator

# K8s Generator

## Overview

This skill provides a complete workflow for generating Kubernetes YAML resources with built-in validation and intelligent CRD support. Generate production-ready manifests for any Kubernetes resource type, with automatic validation and version-aware documentation lookup for custom resources.

## When to Use This Skill

Use this skill when:
- Generating Kubernetes YAML manifests (Deployments, Services, ConfigMaps, etc.)
- Creating custom resources (ArgoCD Applications, Istio VirtualServices, etc.)
- Building production-ready Kubernetes configurations
- Need to ensure YAML validity and K8s API compliance
- Working with CRDs that require documentation lookup

## Core Workflow

Follow this workflow when generating Kubernetes YAML resources:

### 1. Understand Requirements

**Gather information about:**
- Resource type (Deployment, Service, ConfigMap, CRD, etc.)
- Target Kubernetes version (if specified)
- Application requirements (replicas, ports, volumes, etc.)
- Environment-specific needs (namespaces, labels, annotations)
- Custom resource specifications (for CRDs)

**For CRDs specifically:**
- Identify the CRD type and version (e.g., ArgoCD Application v1alpha1, Istio VirtualService v1beta1)
- Determine if documentation is needed (complex CRDs, unfamiliar APIs)

### 2. Fetch CRD Documentation (if needed)

**When dealing with Custom Resource Definitions (CRDs):**

**IMPORTANT: Always consider version compatibility when working with CRDs**

**Step 2a: Identify the CRD and Version**
- Extract the CRD's apiVersion and kind from the user request
- Examples:
  - ArgoCD Application: `apiVersion: argoproj.io/v1alpha1, kind: Application`
  - Istio VirtualService: `apiVersion: networking.istio.io/v1beta1, kind: VirtualService`
  - Cert-Manager Certificate: `apiVersion: cert-manager.io/v1, kind: Certificate`

**Step 2b: Resolve Library ID using Context7 MCP**

Use the `mcp__context7__resolve-library-id` tool to find the correct library:

```
library