OpenShift Deployments Vs DeploymentConfigs¶
Introduction¶
OpenShift deployments manage application rollouts by updating pod templates and creating new ReplicaSets. Verify the Deployment, rollout history, pods, events, and route or service endpoints together.
Core Concepts¶
OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.
Practical Examples¶
oc get deployment web -n app
oc rollout status deployment/web -n app
oc get replicasets -n app -l app=web
oc get pods -n app -l app=web
Example output:
NAME READY UP-TO-DATE AVAILABLE AGE
web 3/3 3 3 18m
deployment "web" successfully rolled out
Verification¶
oc describe deployment web -n app
oc rollout history deployment/web -n app
oc get endpoints web -n app
Common Mistakes¶
- Looking only at the final error and ignoring events.
- Checking the wrong project with oc.
- Changing several objects at once before confirming the current state.
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¶
Summary¶
OpenShift Deployments Vs DeploymentConfigs is best understood through the OpenShift objects involved and the oc commands that verify their current state.