kubernetes

Generate Kubernetes YAML manifests for Deployments, Services, and ConfigMaps.

11|4|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/wpank/ai --skill kubernetes-wpank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes
Source: https://github.com/wpank/ai/tree/main/skills/devops/kubernetes
Command: npx skills add https://github.com/wpank/ai --skill kubernetes-wpank

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the creation of complex Kubernetes manifests, ensuring production-readiness and adherence to best practices, saving developers time and reducing configuration errors.

Core Features & Use Cases

  • Manifest Generation: Create YAML manifests for Deployments, StatefulSets, Services, Ingresses, ConfigMaps, Secrets, and PVCs.
  • Production-Grade Defaults: Includes security contexts, health checks, resource management, and standard labels.
  • Use Case: You need to deploy a new microservice. This Skill guides you through generating the necessary Deployment, Service, and ConfigMap manifests, ensuring they are secure and scalable.

Quick Start

Use the kubernetes skill to generate a deployment manifest for a new web application.

Frequently Asked Questions about kubernetes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate production-ready Kubernetes manifests for a microservice?

Generate production-ready Kubernetes manifests by creating YAML files for Deployments, StatefulSets, Services, Ingresses, ConfigMaps, Secrets, and PVCs with built-in security contexts, health checks, and resource limits.

What is the best way to include security contexts and health checks in K8s YAML?

Include security contexts and health checks in K8s YAML by applying production-grade defaults during manifest generation, ensuring secure scalable deployments with standard labeling conventions.

When do I need a StatefulSet instead of a Deployment in Kubernetes?

You need a StatefulSet instead of a Deployment in Kubernetes when deploying stateful applications requiring stable persistent storage, generating manifests with appropriate PVC configurations and resource management.

Can I generate ConfigMaps and Secrets alongside Kubernetes Deployments?

Yes, you can generate ConfigMaps and Secrets alongside Kubernetes Deployments to inject configuration data and sensitive information into your microservices securely and efficiently.

Does this approach support creating Ingress resources and PVCs for K8s deployments?

Yes, this approach supports creating Ingress resources and PVCs for K8s deployments, generating the necessary YAML manifests to route external traffic and provision persistent storage.

Why do my Kubernetes manifests lack standard labeling conventions and resource limits?

Your Kubernetes manifests lack standard labeling conventions and resource limits because they were not generated with production-grade defaults, which automatically enforce security contexts and resource management.