专家
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需手动接入
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- Docker
- 运行环境要求
- Node.js · Docker
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Kubernetes Specialist
Use this skill for Kubernetes design, architecture, implementation, optimization, and planned changes. For live incidents, unhealthy workloads, CrashLoopBackOff, stuck rollouts, ingress failures, or customer support triage, use `k8s-sre-triage` first.
## Purpose
Provides expert Kubernetes orchestration and cloud-native application expertise with deep knowledge of container orchestration, cluster management, and production-grade deployments. Specializes in Kubernetes architecture, Helm charts, operators, multi-cluster management, and GitOps workflows across EKS, AKS, GKE, and on-premises deployments.
## When to Use
- Designing Kubernetes cluster architecture for production workloads
- Implementing Helm charts, operators, or GitOps workflows (ArgoCD, Flux)
- Troubleshooting design-level or planned-change cluster issues after incident triage has narrowed the fault domain
- Planning Kubernetes upgrades or multi-cluster strategies
- Optimizing resource utilization and cost in Kubernetes environments
- Setting up service mesh (Istio, Linkerd) and observability
- Implementing Kubernetes security and RBAC policies
## Quick Start
**Invoke this skill when:**
- Designing Kubernetes cluster architecture for production workloads
- Implementing Helm charts, operators, or GitOps workflows
- Troubleshooting design-level or planned-change cluster issues after `k8s-sre-triage` has narrowed the fault domain
- Planning Kubernetes upgrades or multi-cluster strategies
- Optimizing resource utilization and cost in Kubernetes environments
**Do NOT invoke when:**
- Simple Docker container needs (use docker commands directly)
- Live Kubernetes incidents or customer support triage (use `k8s-sre-triage` first)
- Cloud infrastructure provisioning (use an installed cloud or infrastructure skill when available)
- Application code debugging (use an installed debugging or application skill when available)
- Database-specific issues (use a database-focused workflow or specialist when available)
## Decision Framework
### Deployment Strategy Selection
```
├─ Zero downtime required?
│ ├─ Instant rollback needed → Blue-Green Deployment
│ │ Pros: Instant switch, easy rollback
│ │ Cons: 2x resources during deployment
│ │
│ ├─ Gradual rollout → Canary Deployment
│ │ Pros: Test with subset of traffic
│ │ Cons: Complex routing setup
│ │
│ └─ Simple updates → Rolling Update (default)
│ Pros: Built-in, no extra resources
│ Cons: Rollback takes time
│
├─ Stateful application?
│ ├─ Database → StatefulSet + PVC
│ │ Pros: Stable network IDs, ordered deployment
│ │ Cons: Complex scaling
│ │
│ └─ Stateless → Deployment
│ Pros: Easy scaling, self-healing
│
└─ Batch processing?
├─ One-time → Job
├─ Scheduled → CronJob
└─ Parallel processing → Job with parallelism
```
### Resource Configuration Matrix
| Workload Type | CPU Request | CPU Limit | Memory Request | Memory Limit |
|---------------|-------------|-----------|----------------|--------------|
| **Web API** | 100m-500m | 1000m | 256Mi-512Mi | 1Gi |
| **Worker** | 500m-1000m | 2000m | 512Mi-1Gi | 2Gi |
| **Database** | 1000m-2000m | 4000m | 2Gi-4Gi | 8Gi |
| **Cache** | 100m-250m | 500m | 1Gi-4Gi | 8Gi |
| **Batch Job** | 500m-2000m | 4000m | 1Gi-4Gi | 8Gi |
### Node Pool Strategy
| Use Case | Instance Type | Scaling | Cost |
|----------|--------------|---------|------|
| **System pods** | t3.large (3 nodes) | Fixed | Low |
| **Applications** | m5.xlarge | Auto 3-20 | Medium |
| **Batch/Spot** | m5.large-2xlarge | Auto 0-50 | Very Low |
| **GPU workloads** | p3.2xlarge | Manual | High |
### Red Flags → Escalate
**STOP and escalate if:**
- Cluster upgrade with breaking API changes (deprecated versions)
- Multi-region active-active requirements
- Compliance requirements (PCI-DSS, HIPAA) need validation
- Custom scheduler or controller development needed
- etcd corruption or cluster state issues
## Quality Checklist
### Cluster Configuration
- [ ] Multi-AZ deployment (nodes spread across availability zones)
- [ ] Node autoscaling configured (Cluster Autoscaler or Karpenter)
- [ ] System node pool with taints (separate critical addons from apps)
- [ ] Encryption enabled (secrets at rest with KMS)
- [ ] Audit logging enabled (API server logs)
### Security
- [ ] Pod Security Standards enforced (restricted or baseline)
- [ ] Network policies configured (default deny + explicit allow)
- [ ] RBAC configured (least privilege for all service accounts)
- [ ] Image scanning enabled (scan for vulnerabilities)
- [ ] Private container registry configured
### Resource Management
- [ ] All pods have resource requests and limits
- [ ] HorizontalPodAutoscalers configured for scalable workloads
- [ ] PodDisruptionBudgets defined (prevent too many pods down)
- [ ] ResourceQuotas set per namespace
- [ ] LimitRanges defined (default limits for pods)
### High Availability
- [ ] Deployments have ≥2 replicas
- [ ] Anti-affinity rules prevent pod co-location
- [ ] Readiness and liveness probes configured
- [ ] PodDisruptionBudgets allow for rolling updates
- [ ] Multi-region cluster (if global scale required)
### Observability
- [ ] Metrics server installed (kubectl top works)
- [ ] Prometheus monitoring application metrics
- [ ] Centralized logging (CloudWatch, Elasticsearch, Loki)
- [ ] Distributed tracing (Jaeger, Tempo)
- [ ] Dashboards for cluster and application health
### Disaster Recovery
- [ ] Velero installed for cluster backups
- [ ] Backup schedule configured (daily minimum)
- [ ] Restore tested (annual drill)
- [ ] etcd backups automated (cloud-managed clusters)
## Additional Resources
- **Detailed Technical Reference**: See [REFERENCE.md](REFERENCE.md)
- **Code Examples & Patterns**: See [EXAMPLES.md](EXAMPLES.md)
---
> Source: [Canepro/codex-skills](https://github.com/Canepro/codex-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
目的
何时使用
快速入门
资源配置矩阵
节点池策略
文件/命令 -> k8s-sre-triage · Batch/Spot · REFERENCE.md · EXAMPLES.md · Canepro/codex-skills · github.com/Canepro/codex-skills
内容校验值 -> dce57a720fd7
当前原文的自动摘译,尚未人工审校。
目的
提供专业的 Kubernetes 编排和云原生应用程序专业知识,以及对容器编排、集群管理和生产级部署的深入了解。专门研究 Kubernetes 架构、Helm 图表、操作员、多集群管理以及跨 EKS、AKS、GKE 和本地部署的 GitOps 工作流程。
何时使用
为生产工作负载设计 Kubernetes 集群架构 实施 Helm 图表、操作符或 GitOps 工作流程(ArgoCD、Flux) 在事件分类缩小故障域后解决设计级或计划变更集群问题 规划 Kubernetes 升级或多集群策略 优化 Kubernetes 环境中的资源利用率和成本
快速入门
在以下情况下调用此技能: 为生产工作负载设计 Kubernetes 集群架构 实施 Helm 图表、操作符或 GitOps 工作流程 在
k8s-sre-triage缩小故障域后对设计级别或计划变更集群问题进行故障排除 规划 Kubernetes 升级或多集群策略资源配置矩阵
工作负载类型 · CPU 请求 · CPU 限制 · 内存请求 · 内存限制 Web API · 100m-500m · 1000m · 256Mi-512Mi · 1Gi Worker · 500m-1000m · 2000m · 512Mi-1Gi · 2Gi 数据库 · 1000m-2000m · 4000m · 2Gi-4Gi · 8Gi 缓存 · 100m-250m · 500m · 1Gi-4Gi · 8Gi
节点池策略
使用案例 · 实例类型 · 扩展 · 成本系统 Pod · t3.large(3 个节点) · 固定 · 低应用程序 · m5.xlarge · 自动 3-20 · 中批量/现货 · m5.large-2xlarge · 自动 0-50 · 非常低 GPU 工作负载 · p3.2xlarge · 手动 · 高