Agent skill
kubernetes-operations
Kubernetes cluster operations on minikube including observability (Grafana, Prometheus, Alertmanager, Loki, Tempo), debugging (kubectl debug, ephemeral containers), and cluster management (ArgoCD). Use when working with cluster/manifests/, Kubernetes workloads, pods, deployments, operators, controllers, or cluster components.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/kubernetes-operations-hippocampus-dev-hippocampus
Metadata
Additional technical details for this skill
- short description
- kubernetes, k8s, minikube, grafana, prometheus, loki, tempo, argocd, pod, クラスタ, 監視, kubectl, deployment
SKILL.md
- Access Grafana at
https://grafana.minikube.127.0.0.1.nip.io - Use EphemeralContainer for in-container debugging
- Disable ArgoCD selfHeal before manual changes, re-enable after
Debugging with Ephemeral Container
kubectl debug <pod-name> -n <namespace> \
--profile=restricted \
--image=ghcr.io/hippocampus-dev/hippocampus/ephemeral-container:main \
--target=<container-name> \
-- <command>
Note: Do not use -it flag when executing commands. It causes output streaming issues.
ArgoCD selfHeal Control
# Disable selfHeal
kubectl patch application <app-name> -n argocd --type=merge \
-p '{"spec":{"syncPolicy":{"selfHeal":false}}}'
# Re-enable selfHeal (after work is complete)
kubectl patch application <app-name> -n argocd --type=merge \
-p '{"spec":{"syncPolicy":{"selfHeal":true}}}'
Observability Signal Overview
| Signal | Backend | Query Language | Use Case |
|---|---|---|---|
| Traces | Tempo | TraceQL | Request flow, latency analysis |
| Metrics | Mimir (Prometheus) | PromQL | Resource usage, alerting |
| Logs | Loki | LogQL | Error investigation, audit |
| Profiles | Pyroscope | Flamegraph UI | CPU/memory hotspots |
| Probes | Blackbox Exporter | PromQL | Endpoint reachability |
Debugging Workflow
- Get query parameters - Check
cluster/manifests/<app>/for namespace, labels,OTEL_SERVICE_NAME - Check dashboard - Open Grafana (kubernetes/namespace, kubernetes/workload, kubernetes/pod)
- Query by symptom - Use appropriate signal based on issue type
| Symptom | Signal | Action |
|---|---|---|
| Errors in logs | Loki → Tempo | Extract traceid, trace in Tempo |
| Latency/5xx | Tempo | Search traces with status = error |
| Resource saturation | Mimir | Query CPU/memory metrics |
| High CPU/memory | Pyroscope | Check flamegraphs |
| Pod not starting | kubectl | kubectl get events -n <namespace> |
Observability Stack Manifests
| Component | Path |
|---|---|
| Grafana | cluster/manifests/grafana/ |
| Tempo | cluster/manifests/tempo/ |
| Mimir | cluster/manifests/mimir/ |
| Loki | cluster/manifests/loki/ |
| Pyroscope | cluster/manifests/pyroscope/ |
| Prometheus | cluster/manifests/prometheus/ |
| Fluentd | cluster/manifests/fluentd/ |
| OpenTelemetry | cluster/manifests/otel-agent/, cluster/manifests/otel-collector/ |
Reference
If writing observability queries: See Queries
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?