- Installs
- 57
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/chaterm/terminal-skills --skill pod-management- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pod-management automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Pod 管理与调试
概述
Pod 生命周期管理、日志查看、exec 调试等技能。
Pod 查看
# 列出 Pod
kubectl get pods
kubectl get pods -o wide # 详细信息
kubectl get pods -A # 所有命名空间
kubectl get pods -n namespace
kubectl get pods -l app=nginx # 按标签过滤
kubectl get pods --field-selector status.phase=Running
# Pod 详情
kubectl describe pod pod-name
kubectl get pod pod-name -o yaml
kubectl get pod pod-name -o jsonpath='{.status.phase}'
日志查看
# 查看日志
kubectl logs pod-name
kubectl logs pod-name -c container-name # 指定容器
kubectl logs pod-name --all-containers # 所有容器
# 实时跟踪
kubectl logs -f pod-name
kubectl logs -f pod-name --since=1h # 最近1小时
kubectl logs -f pod-name --tail=100 # 最后100行
# 上一个容器的日志（崩溃后）
kubectl logs pod-name --previous
# 多 Pod 日志
kubectl logs -l app=nginx # 按标签
kubectl logs -l app=nginx --max-log-requests=10
容器调试
exec 进入容器
# 进入容器
kubectl exec -it pod-name -- /bin/bash
kubectl exec -it pod-name -- sh
kubectl exec -it pod-name -c container-name -- /bin/bash
# 执行命令
kubectl exec pod-name -- ls -la
kubectl exec pod-name -- cat /etc/hosts
kubectl exec pod-name -- env
调试容器
# 使用 debug 容器（K8s 1.18+）
kubectl debug pod-name -it --image=busybox --target=container-name
# 复制 Pod 进行调试
kubectl debug pod-name -it --copy-to=debug-pod --container=debug --image=busybox
# 节点调试
kubectl debug node/node-name -it --image=busybox
端口转发
# 转发到本地
kubectl port-forward pod-name 8080:80
kubectl port-forward pod-name 8080:80 --address 0.0.0.0
# 后台运行
kubectl port-forward pod-name 8080:80 &
Pod 生命周期
创建 Pod
# pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-pod
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:latest
ports:
- containerPort: 80
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 10
periodSeconds: 5
readinessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 5
periodSeconds: 3
kubectl apply -f pod.yaml
kubectl create -f pod.yaml
删除 Pod
kubectl delete pod pod-name
kubectl delete pod pod-name --force --grace-period=0 # 强制删除
kubectl delete pods -l app=nginx # 按标签删除
kubectl delete pods --all -n namespace # 删除所有
Pod 状态
# 查看 Pod 状态
kubectl get pod pod-name -o jsonpath='{.status.phase}'
# 等待 Pod 就绪
kubectl wait --for=condition=Ready pod/pod-name --timeout=60s
# 查看事件
kubectl get events --field-selector involvedObject.name=pod-name
资源管理
查看资源使用
# Pod 资源使用
kubectl top pods
kubectl top pods -n namespace
kubectl top pod pod-name --containers
# 按资源排序
kubectl top pods --sort-by=cpu
kubectl top pods --sort-by=memory
资源配置
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
常见场景
场景 1：排查 Pod 启动失败
# 1. 查看 Pod 状态
kubectl get pod pod-name -o wide
# 2. 查看事件
kubectl describe pod pod-name | grep -A 20 Events
# 3. 查看日志
kubectl logs pod-name
kubectl logs pod-name --previous # 如果容器重启
# 4. 检查镜像
kubectl get pod pod-name -o jsonpath='{.spec.containers[*].image}'
场景 2：排查 CrashLoopBackOff
# 1. 查看退出原因
kubectl describe pod pod-name | grep -A 5 "Last State"
# 2. 查看上一次日志
kubectl logs pod-name --previous
# 3. 检查资源限制
kubectl describe pod pod-name | grep -A 10 "Limits"
# 4. 检查探针配置
kubectl get pod pod-name -o yaml | grep -A 10 "livenessProbe"
场景 3：临时运行调试 Pod
# 运行临时 Pod
kubectl run debug --rm -it --image=busybox -- sh
kubectl run debug --rm -it --image=nicolaka/netshoot -- bash
# 在特定节点运行
kubectl run debug --rm -it --image=busybox --overrides='{"spec":{"nodeName":"node-name"}}' -- sh
场景 4：复制文件
# 从 Pod 复制到本地
kubectl cp pod-name:/path/to/file ./local-file
kubectl cp namespace/pod-name:/path/to/file ./local-file
# 从本地复制到 Pod
kubectl cp ./local-file pod-name:/path/to/file
故障排查
| 状态 | 可能原因 | 排查方法 |
|---|---|---|
| Pending | 资源不足/调度问题 | kubectl describe pod 查看事件 |
| ImagePullBackOff | 镜像拉取失败 | 检查镜像名、仓库认证 |
| CrashLoopBackOff | 应用崩溃 | kubectl logs --previous |
| OOMKilled | 内存超限 | 增加 memory limits |
| Evicted | 节点资源不足 | 检查节点资源、清理 Pod |
| Unknown | 节点失联 | 检查节点状态 |
FAQ
What does the pod-management skill do?
Kubernetes Pod 管理与调试
How do I install pod-management?
Run npx skills add https://github.com/chaterm/terminal-skills --skill pod-management in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pod-management/ (personal) or .claude/skills/pod-management/ (project).
Which AI agents can use pod-management?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pod-management safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pod-management?
It is published by chaterm in chaterm/terminal-skills. It has 57 recorded installs.
More from chaterm/terminal-skills
system-admin
chaterm/terminal-skills
Linux system administration and monitoring
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.