Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Kubernetes Specialist

  • 11.7k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

Kubernetes Specialist provides declarative workload deployment, networking, storage, security, and troubleshooting guidance for container orchestration on Kubernetes clusters.

About

Kubernetes Specialist guides deployment and management of containerized workloads on Kubernetes clusters. Developers use it to author declarative YAML manifests for Deployments, StatefulSets, Services, and Ingress; configure RBAC, NetworkPolicies, and Pod Security Standards; set up persistent storage via PV/PVC; package applications with Helm; troubleshoot pod crashes and resource contention; and implement GitOps pipelines with ArgoCD or Flux. The skill enforces best practices: resource limits on all containers, liveness/readiness probes, least-privilege service accounts, secrets management, and network isolation policies. Validation uses kubectl rollout status, pod event streaming, and log inspection.

  • Author declarative YAML for Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs with resource requests/limits and
  • Implement least-privilege RBAC (ServiceAccount, Role, RoleBinding) and NetworkPolicies for default-deny + explicit allow
  • Configure persistent storage (PV, PVC, StorageClasses, CSI drivers) and manage secrets separately from ConfigMaps
  • Create and test Helm charts for application packaging, including values, templates, and hooks
  • Troubleshoot via kubectl rollout status, pod events, logs, describe, and top; roll back failed deployments

Kubernetes Specialist by the numbers

  • 11,718 all-time installs (skills.sh)
  • +215 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #20 of 1,453 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

kubernetes-specialist capabilities & compatibility

Capabilities
author declarative yaml for all kubernetes workl · design and implement rbac and networkpolicies · configure persistent storage and manage secrets · create and test helm charts · troubleshoot pod crashes, logs, and events · optimize resource requests/limits and costs · implement gitops pipelines and multi cluster man
Works with
kubernetes · github · gitlab
Use cases
devops · ci cd · security audit · debugging · orchestration
Platforms
macOS · Windows · Linux · WSL
Runs
Runs locally
Pricing
Free
npx skills add https://github.com/jeffallan/claude-skills --skill kubernetes-specialist

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs11.7k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

What it does

Create and manage Kubernetes workloads, networking, storage, and security policies declaratively via YAML manifests and kubectl.

Who is it for?

Deploying microservices, stateful applications, multi-cluster setups; enforcing security policies; implementing GitOps; right-sizing workloads; troubleshooting container crashes.

Skip if: Non-containerized legacy applications; Kubernetes cluster provisioning (use cloud-architect or terraform-engineer); local development without container orchestration.

When should I use this skill?

Deploying workloads, configuring networking, managing secrets, setting up persistent storage, troubleshooting pod issues, implementing RBAC, creating Helm charts, optimizing resource usage.

What you get

Production-ready Kubernetes manifests with proper resource limits, RBAC, NetworkPolicies, health checks, and GitOps integration; rapid troubleshooting of pod failures and resource issues.

  • ConfigMap YAML
  • Secret manifests
  • Namespace-scoped workload definitions

By the numbers

  • Covers 11 reference topics: Workloads, Networking, Configuration, Storage, Helm, Troubleshooting, Operators, Service Mes
  • Includes MUST DO constraints (resource limits, probes, secrets, RBAC, NetworkPolicies) and MUST NOT DO anti-patterns (pr
  • Provides 3 complete YAML patterns: Deployment with security context, minimal RBAC, and NetworkPolicy default-deny

Files

SKILL.mdMarkdownGitHub ↗

Kubernetes Specialist

When to Use This Skill

  • Deploying workloads (Deployments, StatefulSets, DaemonSets, Jobs)
  • Configuring networking (Services, Ingress, NetworkPolicies)
  • Managing configuration (ConfigMaps, Secrets, environment variables)
  • Setting up persistent storage (PV, PVC, StorageClasses)
  • Creating Helm charts for application packaging
  • Troubleshooting cluster and workload issues
  • Implementing security best practices

Core Workflow

1. Analyze requirements — Understand workload characteristics, scaling needs, security requirements 2. Design architecture — Choose workload types, networking patterns, storage solutions 3. Implement manifests — Create declarative YAML with proper resource limits, health checks 4. Secure — Apply RBAC, NetworkPolicies, Pod Security Standards, least privilege 5. Validate — Run kubectl rollout status, kubectl get pods -w, and kubectl describe pod <name> to confirm health; roll back with kubectl rollout undo if needed

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Workloadsreferences/workloads.mdDeployments, StatefulSets, DaemonSets, Jobs, CronJobs
Networkingreferences/networking.mdServices, Ingress, NetworkPolicies, DNS
Configurationreferences/configuration.mdConfigMaps, Secrets, environment variables
Storagereferences/storage.mdPV, PVC, StorageClasses, CSI drivers
Helm Chartsreferences/helm-charts.mdChart structure, values, templates, hooks, testing, repositories
Troubleshootingreferences/troubleshooting.mdkubectl debug, logs, events, common issues
Custom Operatorsreferences/custom-operators.mdCRD, Operator SDK, controller-runtime, reconciliation
Service Meshreferences/service-mesh.mdIstio, Linkerd, traffic management, mTLS, canary
GitOpsreferences/gitops.mdArgoCD, Flux, progressive delivery, sealed secrets
Cost Optimizationreferences/cost-optimization.mdVPA, HPA tuning, spot instances, quotas, right-sizing
Multi-Clusterreferences/multi-cluster.mdCluster API, federation, cross-cluster networking, DR

Constraints

MUST DO

  • Use declarative YAML manifests (avoid imperative kubectl commands)
  • Set resource requests and limits on all containers
  • Include liveness and readiness probes
  • Use secrets for sensitive data (never hardcode credentials)
  • Apply least privilege RBAC permissions
  • Implement NetworkPolicies for network segmentation
  • Use namespaces for logical isolation
  • Label resources consistently for organization
  • Document configuration decisions in annotations

MUST NOT DO

  • Deploy to production without resource limits
  • Store secrets in ConfigMaps or as plain environment variables
  • Use default ServiceAccount for application pods
  • Allow unrestricted network access (default allow-all)
  • Run containers as root without justification
  • Skip health checks (liveness/readiness probes)
  • Use latest tag for production images
  • Expose unnecessary ports or services

Common YAML Patterns

Deployment with resource limits, probes, and security context

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app
  namespace: my-namespace
  labels:
    app: my-app
    version: "1.2.3"
spec:
  replicas: 3
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
        version: "1.2.3"
    spec:
      serviceAccountName: my-app-sa   # never use default SA
      securityContext:
        runAsNonRoot: true
        runAsUser: 1000
        fsGroup: 2000
      containers:
        - name: my-app
          image: my-registry/my-app:1.2.3   # never use latest
          ports:
            - containerPort: 8080
          resources:
            requests:
              cpu: "100m"
              memory: "128Mi"
            limits:
              cpu: "500m"
              memory: "512Mi"
          livenessProbe:
            httpGet:
              path: /healthz
              port: 8080
            initialDelaySeconds: 15
            periodSeconds: 20
          readinessProbe:
            httpGet:
              path: /ready
              port: 8080
            initialDelaySeconds: 5
            periodSeconds: 10
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            capabilities:
              drop: ["ALL"]
          envFrom:
            - secretRef:
                name: my-app-secret   # pull credentials from Secret, not ConfigMap

Minimal RBAC (least privilege)

apiVersion: v1
kind: ServiceAccount
metadata:
  name: my-app-sa
  namespace: my-namespace
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: my-app-role
  namespace: my-namespace
rules:
  - apiGroups: [""]
    resources: ["configmaps"]
    verbs: ["get", "list"]   # grant only what is needed
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: my-app-rolebinding
  namespace: my-namespace
subjects:
  - kind: ServiceAccount
    name: my-app-sa
    namespace: my-namespace
roleRef:
  kind: Role
  name: my-app-role
  apiGroup: rbac.authorization.k8s.io

NetworkPolicy (default-deny + explicit allow)

# Deny all ingress and egress by default
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: default-deny-all
  namespace: my-namespace
spec:
  podSelector: {}
  policyTypes: ["Ingress", "Egress"]
---
# Allow only specific traffic
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-my-app
  namespace: my-namespace
spec:
  podSelector:
    matchLabels:
      app: my-app
  policyTypes: ["Ingress"]
  ingress:
    - from:
        - podSelector:
            matchLabels:
              app: frontend
      ports:
        - protocol: TCP
          port: 8080

Validation Commands

After deploying, verify health and security posture:

# Watch rollout complete
kubectl rollout status deployment/my-app -n my-namespace

# Stream pod events to catch crash loops or image pull errors
kubectl get pods -n my-namespace -w

# Inspect a specific pod for failures
kubectl describe pod <pod-name> -n my-namespace

# Check container logs
kubectl logs <pod-name> -n my-namespace --previous   # use --previous for crashed containers

# Verify resource usage vs. limits
kubectl top pods -n my-namespace

# Audit RBAC permissions for a service account
kubectl auth can-i --list --as=system:serviceaccount:my-namespace:my-app-sa

# Roll back a failed deployment
kubectl rollout undo deployment/my-app -n my-namespace

Output Templates

When implementing Kubernetes resources, provide: 1. Complete YAML manifests with proper structure 2. RBAC configuration if needed (ServiceAccount, Role, RoleBinding) 3. NetworkPolicy for network isolation 4. Brief explanation of design decisions and security considerations

Documentation

Related skills

Forks & variants (1)

Kubernetes Specialist has 1 known copy in the catalog totaling 144 installs. They canonicalize to this original listing.

How it compares

Pick kubernetes-specialist for agent-guided YAML manifest authoring; use Helm or Kustomize when templating and overlay management across many environments is the primary need.

FAQ

Should I use ConfigMap or Secret for database credentials?

Always use Secret for credentials. Never store secrets in ConfigMaps or plain environment variables; pull via secretRef in pod spec.

What resource limits should I set?

Set requests and limits on all containers based on workload testing. Requests guarantee scheduling; limits prevent runaway consumption. Use kubectl top pods to monitor actual usage.

How do I roll back a failed deployment?

Use kubectl rollout undo deployment/<name> to revert to the previous replica set. Monitor rollout status with kubectl rollout status deployment/<name>.

Is Kubernetes Specialist safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

DevOps & CI/CDdeployinframonitoring

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.