OpenShift Projects Vs Namespaces¶
Introduction¶
OpenShift projects are Kubernetes namespaces with additional project metadata and access workflows. Use projects to isolate teams, quotas, role bindings, and application resources.
Core Concepts¶
OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.
Practical Examples¶
oc new-project app-dev
oc project app-dev
oc get rolebinding -n app-dev
oc describe project app-dev
Example output:
Now using project "app-dev" on server "https://api.ocp.example.com:6443".
NAME DISPLAY NAME STATUS
app-dev Active
Verification¶
oc get project app-dev
oc auth can-i create pods -n app-dev
oc get resourcequota -n app-dev
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 Projects Vs Namespaces is best understood through the OpenShift objects involved and the oc commands that verify their current state.