Kubernetes / Deployments, Scheduling & Batch Workloads
Compare a Pod's running image identity with the intended release
A mutable tag can produce different content across restarts or nodes. Capture the runtime image identifier rather than only the tag.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app get pod web-0 -o jsonpath='{.spec.containers[*].image}{" "}{.status.containerStatuses[*].imageID}'Read the result
The specification and status show requested references and runtime-resolved image identities. Multi-container and platform-specific manifests require matching the correct container.
Resolve and verify
Compare verified release digests and registry provenance, then use an approved immutable reference where supported. Validate the replacement rollout and application version.
Before changing production
Do not assume equal tags mean equal binaries or overwrite a production tag to hide a release mismatch.