← All insightsObservability

Monitoring and observability for Kubernetes

Nir Geier, CodeWizard · 5 September 2026 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of Kubernetes and turn them into alerts that mean something.

Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.

What to watch

  • Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
  • Separate config (ConfigMap) from secrets and mount them, don't bake them in
  • Use readiness probes to gate traffic and PodDisruptionBudgets for safe drains
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
kubectl apply -f deploy.yaml
kubectl rollout status deploy/web
kubectl get pods -l app=web
kubectl logs deploy/web
kubectl rollout undo deploy/web   # roll back the last change

Keep it healthy

  • Enforce least privilege with RBAC and disable the default ServiceAccount token mount
  • Apply NetworkPolicies to default-deny east-west traffic

Want senior help putting Kubernetes to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult