Cloud DevOps Signal Assessment

Roll back immediately, then investigate later

Check the deployment status and events, then drill into the failing pods

Restart the nodes to clear any cluster issues

Increase replica count to overwhelm the issue

Run kubectl logs  and kubectl describe pod  to inspect logs, events, probes, and image/mount errors

Change the service selector to point away from the new pods

ReplicaSet was created but readiness probes never pass

New pods never become Ready due to readiness probe failures, image pull errors, or resource constraints

Check service selectors, endpoints, and ingress/controller logs

Increase initialDelaySeconds and timeoutSeconds and redeploy

Remove readiness probes so the rollout completes

Inspect probe configuration, app health endpoint behavior, and container startup logs, then adjust probe values only if needed

Roll back → check logs → check events → check probes

Check cluster health → restart nodes → redeploy

Run kubectl rollout status, then kubectl describe deploy/rs/pod, check logs, review probe failures and events, verify service endpoints/ingress, and roll back only if blast radius increases

Disable probes → redeploy → tune resources → re-enable probes

Scale up replicas → drain nodes → redeploy

Move to remote state with locking such as S3 with DynamoDB or Terraform Cloud and isolate environments per workspace

Increase instance size of the state backend

Image was built but not pushed to the correct registry or a tag mismatch occurred

Horizontal Pod Autoscaler misconfiguration

Increase replica count to use allocated CPU

Right-size resource requests and limits and evaluate cluster autoscaler and node pool sizing

Add structured logging and distributed tracing to identify latency bottlenecks