spec and status

The two halves of most Kubernetes objects: spec is what you ask for, and status is what the cluster reports is actually true.

In more detail

You write the spec; controllers and the kubelet write the status. Comparing the two is the heart of troubleshooting, because a gap between them points at the component that has not finished its job. kubectl describe shows both, followed by recent events.

Example

kubectl get pod web -o jsonpath='{.status.phase}'

Related terms

Taught in

References

Certification courses