smithery/NickCrew

kubernetes-deployment-patterns

Kubernetes deployment strategies and workload patterns for production-grade applications. Use when deploying to Kubernetes, implementing rollout strategies, or designing cloud-native application architectures.

Installation

$ npx skills add smithery/NickCrew --skill kubernetes-deployment-patterns

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/NickCrew · top by installs.

npx skills add smithery/NickCrew

Browse all from smithery/NickCrew

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,668 B
  • docs SUMMARY.md 247 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Kubernetes Deployment Patterns

Expert guidance for production-grade Kubernetes deployments covering deployment strategies, workload types, configuration management, resource optimization, and autoscaling patterns for cloud-native applications.

When to Use This Skill

  • Implementing deployment strategies (rolling updates, blue-green, canary releases)
  • Choosing appropriate workload types (Deployment, StatefulSet, DaemonSet, Job)
  • Designing rollout strategies for zero-downtime deployments
  • Implementing configuration management with ConfigMaps and Secrets
  • Setting up resource management and autoscaling (HPA, VPA)
  • Configuring health checks and probe strategies
  • Designing highly available applications on Kubernetes
  • Implementing batch processing and scheduled jobs

Core Concepts

Deployment Strategies

Rolling Update: Gradually replace old pods with new ones (zero-downtime, default) Recreate: Terminate all old pods before creating new ones (brief downtime) Blue-Green: Run two environments, switch traffic instantly (2x resources) Canary: Gradually shift traffic to new version while monitoring (risk mitigation)

Workload Types

Deployment: Stateless applications (web servers, APIs, microservices) StatefulSet: Stateful applications (databases, message queues) DaemonSet: Node-level services (log collectors, monitoring agents) Job: One-time tasks (batch processing, migrations) CronJob: Scheduled tasks (backups, periodic reports)

Resource Management

Requests: Guaranteed resources for scheduling Limits: Maximum resources enforced by kubelet HPA: Horizontal Pod Autoscaler (scale replicas based on metrics) VPA: Vertical Pod Autoscaler (adjust resource requests/limits)

Quick Reference

Task Load reference
Deployment strategies (rolling, blue-green, canary) skills/kubernetes-deployment-patterns/references/deployment-strategies.md
Workload types (Deployment, StatefulSet, DaemonSet, Job) skills/kubernetes-deployment-patterns/references/workload-types.md
Configuration management (ConfigMaps, Secrets) skills/kubernetes-deployment-patterns/references/configuration-management.md
Resource management and autoscaling (HPA, VPA) skills/kubernetes-deployment-patterns/references/resource-management.md
Production best practices and security skills/kubernetes-deployment-patterns/references/production-best-practices.md

Workflow

1. Choose Deployment Strategy

# Rolling update for standard deployments
strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 1
    maxUnavailable: 0

# Recreate for incompatible versions
strategy:
  type: Recreate

2. Select Workload Type

  • Stateless? → Use Deployment
  • Stateful with persistent identity? → Use StatefulSet
  • One pod per node? → Use DaemonSet
  • Run to completion? → Use Job
  • Run on schedule? → Use CronJob

3. Configure Resources

resources:
  requests:
    memory: "256Mi"
    cpu: "250m"
  limits:
    memory: "512Mi"
    cpu: "1000m"

4. Add Configuration

# ConfigMap for non-sensitive config
envFrom:
- configMapRef:
    name: app-config

# Secret for sensitive data
env:
- name: DB_PASSWORD
  valueFrom:
    secretKeyRef:
      name: db-credentials
      key: password

5. Implement Health Checks

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

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

6. Enable Autoscaling

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
spec:
  scaleTargetRef:
    kind: Deployment
    name: app
  minReplicas: 2
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 70

Common Mistakes

  1. Using latest tag: Always use specific version tags for reproducibility
  2. No resource limits: Can cause resource starvation and cluster instability
  3. Missing health checks: Kubernetes can't manage pod health without probes
  4. Single replica in production: No high availability or resilience
  5. Secrets in ConfigMaps: Use Secrets for sensitive data, not ConfigMaps
  6. No update strategy: Leads to unpredictable deployment behavior
  7. Running as root: Security vulnerability, violates least privilege
  8. No monitoring: Can't detect or debug issues in production

Resources