OpenShift Rollout Restart¶

Introduction¶

Rollout commands restart, monitor, and inspect workload updates. Use them after image, environment, probe, or resource changes to confirm that new pods are healthy.

Before You Start¶

Make sure you are in the correct project and know whether the application is driven by a Deployment, DeploymentConfig, BuildConfig, ImageStream, or external registry image.

Practical Examples¶

oc rollout restart deployment/web -n app

oc rollout status deployment/web -n app

oc rollout history deployment/web -n app

oc get replicasets -n app -l app=web

Example output:

deployment.apps/web restarted
deployment "web" successfully rolled out

Verification¶

oc rollout status deployment/web -n app

oc get pods -n app -l app=web

oc describe deployment web -n app

Troubleshooting¶

Watch rollout status, inspect new ReplicaSets and pods, then check events and logs if the rollout does not complete.

Common Mistakes¶

• Restarting a deployment to hide a failing probe or bad image.
• Ignoring rollout timeout messages.
• Deleting ReplicaSets manually during rollout troubleshooting.

Quick Checklist¶

• Confirm the active project.
• Inspect the exact object named in the error.
• Read recent events.
• Apply one focused fix.
• Verify status after the change.

Related Guides¶

• Openshift New App Explained
• Openshift Imagestream Explained
• Openshift Application Deployment Checklist

Summary¶

OpenShift Rollout Restart should be verified with commands that match the OpenShift object being changed or investigated.