k8s

muzhicaomingwang's avatarfrom muzhicaomingwang

Kubernetes ops skill for deploying, operating, and troubleshooting services on Kubernetes. Use for tasks like writing manifests/Helm, configuring deployments/services/ingress, autoscaling, observability, RBAC, secrets/configmaps, rollout/rollback, incident debugging, and production readiness checks.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Cloud Infrastructure]

When & Why to Use This Skill

This Claude skill automates Kubernetes operations, providing expert assistance in deploying, managing, and troubleshooting containerized services. It streamlines the creation of manifests and Helm charts, configures networking and autoscaling, and ensures production readiness through rigorous observability and security best practices, significantly reducing the complexity of cloud-native infrastructure management.

Use Cases

  • Automated Deployment Design: Generate optimized Kubernetes manifests or Helm templates for stateless and stateful applications, including resource requests/limits, QoS settings, and health probes.
  • Incident Debugging and Troubleshooting: Rapidly diagnose service outages, image pull errors, or performance bottlenecks by analyzing pod logs, events, and resource throttling to provide actionable fixes.
  • Networking and Security Configuration: Configure complex networking components like Ingress controllers, TLS termination, and NetworkPolicies, while managing sensitive data via Secrets and ConfigMaps.
  • Resilience and Scaling: Implement Horizontal Pod Autoscaling (HPA) based on custom metrics and design graceful shutdown procedures to maintain high availability during traffic spikes or maintenance.
  • Release Operations: Execute and verify rolling updates or canary deployments with comprehensive rollback plans and post-deployment smoke tests.
namek8s
descriptionKubernetes ops skill for deploying, operating, and troubleshooting services on Kubernetes. Use for tasks like writing manifests/Helm, configuring deployments/services/ingress, autoscaling, observability, RBAC, secrets/configmaps, rollout/rollback, incident debugging, and production readiness checks.

k8s

Use this skill for Kubernetes 运维与发布相关工作。

Defaults / assumptions to confirm

  • Cluster type: managed (EKS/GKE/ACK) vs self-hosted
  • Packaging: raw YAML vs Helm vs Kustomize
  • Ingress: NGINX/ALB/APISIX/Istio
  • Observability stack: Prometheus/Grafana, Loki/ELK, tracing

Workflow

  1. Understand service requirements
  • Ports, protocols, health checks, resources (CPU/mem), storage needs.
  • SLOs: latency, availability, RPO/RTO.
  • Dependencies: DB, cache, MQ, external APIs.
  1. Deployment design
  • Use Deployment for stateless; StatefulSet for stable identities/storage.
  • Define readinessProbe and livenessProbe (and startupProbe if needed).
  • Set resources.requests/limits and choose appropriate QoS.
  • Use PodDisruptionBudget for availability during maintenance.
  1. Config & secrets
  • Config: ConfigMap (non-sensitive), mounted or env.
  • Secrets: Secret (sensitive) + external secret manager if available.
  • Never commit plaintext secrets; prefer sealed/external secrets.
  1. Networking
  • Service types and DNS.
  • Ingress/Gateway routing, TLS termination, timeouts.
  • NetworkPolicy if cluster enforces it.
  1. Scaling & resilience
  • HPA based on CPU/memory/custom metrics.
  • Graceful shutdown (preStop, terminationGracePeriodSeconds).
  • Retry/backoff at client; avoid retry storms.
  1. Observability
  • Standard logs with correlation IDs.
  • Metrics: RPS, p95 latency, error rate, saturation.
  • Alerts and dashboards; runbook links.
  1. Release operations
  • Rolling updates, canary/blue-green if needed.
  • kubectl rollout status + rollback plan.
  • Post-deploy verification checks and smoke tests.
  1. Troubleshooting checklist
  • kubectl get/describe pods, events, and logs.
  • Check probes, image pull, env/config, DNS, network, and resource throttling.
  • For performance: node pressure, HPA behavior, GC/heap, connection pool limits.

Output expectations when making changes

  • Provide manifests (or Helm values/templates) + brief deployment notes.
  • Include resource sizing rationale and probe settings.
  • Include rollback instructions and verification steps.