kubernetes-specialist

To generate Kubernetes manifests with Kustomize, this Skill creates an infra/k8s/ directory containing a base layer plus development and production overlays. It interactively collects your project name, namespace, ports, health path, and ingress hosts to produce Deployment, Service, ConfigMap, Ingress, and HPA resources.

The best way to structure Kustomize overlays is using a canonical infra/k8s/ layout that separates base resources from environment-specific configurations. This approach generates distinct development and production overlays with sensible defaults to eliminate manual, error-prone manifest authoring.

You do not need to manually configure HPA and Ingress resources when initializing Kubernetes manifests. The Skill automatically generates these standard resources alongside Deployment, Service, and ConfigMap manifests with placeholders and sensible defaults during the interactive input flow.

You can safely create Kubernetes manifests for an existing project because the Skill enforces safety rules that never overwrite existing files without explicit confirmation. It also enforces lowercase-dashed project naming conventions and includes TODOs in ConfigMaps to guide manual adjustments.

Your Kubernetes ConfigMap needs TODOs and separate secret names to enforce safe configuration practices and prevent hardcoded sensitive values. The Skill adds comments for secrets and requires explicit secret names during the interactive collection process to ensure proper deployment hygiene.

To set up a canonical k8s directory layout for a new service deployment, provide the project name, namespace, application and health ports, health path, configmap defaults, and ingress hosts. The Skill then generates the complete Kustomize base and environment overlays to enable consistent CI/CD integration.