- Home
- Skills
- Akin Ozer
- Cc Devops Skills
- K8s Yaml Generator
k8s-yaml-generator_skill
- HCL
83
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill akin-ozer/cc-devops-skills --skill k8s-yaml-generator- SKILL.md14.4 KB
Overview
This skill is a comprehensive toolkit for generating, validating, and managing Kubernetes YAML resources. It produces production-ready manifests for core resources and CRDs, with version-aware documentation lookup and automatic validation. Use it to streamline manifest creation while enforcing API compatibility and best practices.
How this skill works
The skill gathers resource requirements (type, Kubernetes version, replicas, ports, environment metadata) and, for CRDs, resolves and fetches authoritative docs using a library lookup. It generates YAML using Kubernetes best practices, then invokes an automated validator to lint syntax, check schemas, and run dry-run validation when possible. After validation passes, it returns the validated manifest with a concise summary and suggested next steps.
When to use it
- Creating Deployments, Services, ConfigMaps, StatefulSets, Ingress, or Namespace manifests
- Authoring or updating Custom Resource Definitions (ArgoCD, Istio, cert-manager, etc.)
- Preparing production-ready configurations with resource limits, probes, and security contexts
- Ensuring API-version compatibility for a specific Kubernetes target version
- Validating YAML before apply or CI/CD pipeline promotion
Best practices
- Specify explicit apiVersion and avoid deprecated APIs
- Include recommended app.kubernetes.io labels and meaningful annotations
- Define resource requests and limits, liveness/readiness probes, and namespaces
- Follow least-privilege security: non-root containers, PodSecurity, and scoped RBAC
- For CRDs, fetch versioned documentation and include all required fields; add comments for complex specs
Example use cases
- Generate a multi-resource bundle (ConfigMap + Deployment + Service) with consistent labels and dependency ordering
- Create an ArgoCD Application CRD manifest using the targeted argoproj version docs
- Produce an Istio VirtualService for routing with version-aware spec fields
- Generate a cert-manager Certificate manifest tied to a ClusterIssuer and DNS names
- Validate YAML in CI using the integrated k8s-yaml-validator before kubectl apply
FAQ
The skill falls back to targeted web searches that include the CRD name and version, and advises trying alternative project names or checking upstream docs directly.
How is validation performed?
Validation runs yamllint for syntax, kubeconform for API/schema checks, best-practice checks, and an optional dry-run against an available cluster; errors are returned with actionable fixes.
Can I target a specific Kubernetes version?
Yes. Specify the target version and the skill will choose appropriate apiVersion values, note deprecations, and fetch version-matching CRD docs when required.