kubernetes-manifests

Use when writing and deploying Kubernetes manifests for container orchestration.

⭐47stars🔀5forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines the process of writing, deploying, and validating Kubernetes manifests for efficient container orchestration. It provides comprehensive guidance on creating robust YAML configurations for essential resources like Deployments, Services, and ConfigMaps, while integrating industry best practices for resource management and cluster reliability.

Use Cases

  • 1. Automated Manifest Generation: Rapidly create standardized and error-free YAML files for various Kubernetes resource types to accelerate the development-to-deployment pipeline.
  • 2. Infrastructure Optimization: Implement precise resource requests and limits to ensure efficient CPU and memory utilization across the cluster.
  • 3. High Availability Configuration: Define liveness and readiness probes to automate health checks and ensure seamless application self-healing.
  • 4. Pre-deployment Validation: Utilize dry-run commands and validation tools to identify syntax errors and configuration flaws before they impact production environments.
  • 5. Secure Secret Management: Configure Kubernetes Secrets and ConfigMaps to manage sensitive data and environment variables securely within containerized applications.
namekubernetes-manifests
descriptionUse when writing and deploying Kubernetes manifests for container orchestration.
allowed-tools[]

Kubernetes Manifests

Understanding and writing Kubernetes manifest files.

Basic Structure

apiVersion: v1
kind: Pod
metadata:
  name: my-app
  namespace: default
  labels:
    app: my-app
spec:
  containers:
  - name: app
    image: nginx:latest
    ports:
    - containerPort: 80

Common Resource Types

Deployment

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
      - name: app
        image: myapp:1.0.0
        resources:
          requests:
            memory: "64Mi"
            cpu: "250m"
          limits:
            memory: "128Mi"
            cpu: "500m"

Service

apiVersion: v1
kind: Service
metadata:
  name: my-app-service
spec:
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
  type: LoadBalancer

ConfigMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
data:
  database.url: "postgres://db:5432"
  log.level: "info"

Secret

apiVersion: v1
kind: Secret
metadata:
  name: app-secrets
type: Opaque
data:
  password: cGFzc3dvcmQxMjM=  # base64 encoded

Best Practices

Resource Requests and Limits

Always define resource requests and limits:

resources:
  requests:
    memory: "64Mi"
    cpu: "250m"
  limits:
    memory: "128Mi"
    cpu: "500m"

Liveness and Readiness Probes

livenessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 30
  periodSeconds: 10

readinessProbe:
  httpGet:
    path: /ready
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 5

Labels and Selectors

Use consistent labeling:

metadata:
  labels:
    app: my-app
    version: v1
    environment: production

Validation

# Validate manifest syntax
kubectl apply --dry-run=client -f manifest.yaml

# Validate with kubeconform
kubeconform manifest.yaml

# Validate against live cluster
kubectl apply --dry-run=server -f manifest.yaml