kubernetes-manifests

Author Kubernetes manifests with resource limits, health probes, and security practices.

3|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jon23d/skillz --skill kubernetes-manifests-jon23d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-manifests
Source: https://github.com/jon23d/skillz/tree/main/skills/kubernetes-manifests
Command: npx skills add https://github.com/jon23d/skillz --skill kubernetes-manifests-jon23d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidelines for creating and reviewing Kubernetes manifests, ensuring they are robust, maintainable, and adhere to best practices, thereby preventing common deployment issues and improving cluster stability.

Core Features & Use Cases

  • Manifest Structure: Guides on organizing Kubernetes manifests within a repository.
  • Resource Management: Enforces the use of resource requests and limits for containers.
  • Health Probes: Mandates liveness and readiness probes for application health monitoring.
  • Security Best Practices: Recommends running containers as non-root and using read-only root filesystems.
  • Provider Agnosticism: Advises against cloud-specific annotations to maintain portability.
  • Use Case: When developing a new microservice, use this Skill to generate and validate its Deployment, Service, ConfigMap, and HorizontalPodAutoscaler manifests, ensuring they meet production readiness standards.

Quick Start

Use the kubernetes-manifests skill to generate a basic Kubernetes Deployment manifest for a new service named 'my-app'.

Frequently Asked Questions about kubernetes-manifests

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

FAQPage Schema
What are the best practices for writing Kubernetes manifests?

Best practices for Kubernetes manifests include defining resource requests and limits, setting liveness and readiness probes, and running containers as non-root with read-only root filesystems to ensure reliability and maintainability.

How do I structure Kubernetes manifests in a repository?

Structure Kubernetes manifests by organizing them within your repository using provider-agnostic conventions, avoiding cloud-specific annotations to maintain application portability across different cluster environments.

Do I need resource requests and limits for Kubernetes deployments?

Yes, you need resource requests and limits for Kubernetes deployments to enforce resource management standards, which prevents common deployment issues and improves overall cluster stability.

How do health probes improve Kubernetes deployment reliability?

Health probes improve Kubernetes deployment reliability by monitoring application health through liveness and readiness checks, ensuring traffic only routes to ready pods and restarting unresponsive containers automatically.

Can I use cloud-specific annotations in Kubernetes manifests?

You should avoid cloud-specific annotations in Kubernetes manifests to maintain provider agnosticism, ensuring your deployments remain portable and readable across different infrastructure providers.

What security settings should I apply to Kubernetes containers?

Apply security settings that run containers as non-root users and utilize read-only root filesystems, adhering to Kubernetes security best practices to protect application deployments.