OpenShift New App Explained¶

Introduction¶

oc new-app creates OpenShift application objects from source, image, or template input. It is useful for quick starts, but production teams should review and commit the generated YAML.

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 new-app registry.access.redhat.com/ubi9/httpd-24 --name=web -n app

oc get deployment,service -n app -l app=web

oc expose service/web -n app

oc get route web -n app

Example output:

deployment.apps/web created
service/web created
route.route.openshift.io/web exposed

Verification¶

oc get all -n app -l app=web

oc describe deployment web -n app

oc get route web -n app

Troubleshooting¶

After oc new-app creates objects, inspect each generated Deployment, Service, ImageStream, and Route before treating the application as production-ready.

Common Mistakes¶

• Treating generated objects as production-ready without review.
• Exposing a service before checking endpoints.
• Forgetting to set resource requests and probes.

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 Imagestream Explained
• Openshift Application Deployment Checklist

Summary¶

OpenShift New App Explained should be verified by reviewing the generated application objects and confirming that pods, services, and routes work together.