kubernetes-operations

---

name: kubernetes-operations description: 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. keywords: kubernetes, k8s, minikube, grafana, prometheus, loki, tempo, argocd, pod, クラスタ, 監視, kubectl, deployment

• Access Grafana at 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

Copykubectl 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

Copy# 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

Debugging Workflow

1. Get query parameters - Check cluster/manifests/<app>/ for namespace, labels, OTEL_SERVICE_NAME
2. Check dashboard - Open Grafana (kubernetes/namespace, kubernetes/workload, kubernetes/pod)
3. Query by symptom - Use appropriate signal based on issue type

Observability Stack Manifests

Reference

If writing observability queries: See Queries