OpenShift Interview FAQs: Quick-Answer Cheat Sheet (2027)
OpenShift interview cheat sheet: 31 short answers on projects, routes, SCCs, builds, image streams, Operators and oc commands, plus scenarios.
OpenShift interviews test whether you understand what Red Hat adds on top of Kubernetes: projects, routes, security context constraints, builds and image streams, Operators, and the oc CLI. Give a one-line answer, name the OpenShift object involved, and mention the command you would run to check it.
This is a revision sheet, built for the last hour before an interview. Each answer is short on purpose. For the full bank, use our 120+ OpenShift interview questions. If your panel is likely to go deep, practise with scenario-based OpenShift questions and the advanced set for experienced engineers. For how the platform sits on Red Hat Enterprise Linux, read how RHEL 10 fits with Kubernetes and OpenShift.
Key takeaways
- OpenShift is a Kubernetes distribution. Everything you know about pods, Deployments and Services still applies.
- The OpenShift-specific objects that come up most are Projects, Routes, SecurityContextConstraints, BuildConfigs, ImageStreams and Operators.
- Red Hat deprecated the DeploymentConfig API in OpenShift Container Platform 4.14 and recommends standard Kubernetes Deployments.
- Routes support edge, passthrough and re-encrypt TLS termination.
- Say which
occommand you would use to verify each answer. It shows hands-on experience.
OpenShift versus plain Kubernetes
| Need | Upstream Kubernetes | OpenShift |
|---|---|---|
| Namespace with extra metadata and self-service | Namespace | Project |
| External HTTP(S) access | Ingress or Gateway API | Route (Ingress also supported) |
| Pod security controls | Pod Security Admission | SecurityContextConstraints |
| Build images in-cluster | External CI | BuildConfig, including Source-to-Image |
| Track image tags | None built in | ImageStream |
| CLI | kubectl | oc (kubectl commands plus OpenShift extras) |
Beginner FAQs
- What is OpenShift?
Red Hat's Kubernetes platform. It adds developer tools, built-in security defaults, a web console, an integrated registry and Operator-based lifecycle management. - What is OKD?
The community distribution of Kubernetes that OpenShift is built from. - What is a Project?
A Kubernetes namespace with additional annotations and access control. Create one withoc new-project web-team-dev. - How do you log in from the CLI?
oc loginwith the API server URL and your credentials or token.oc whoamiconfirms who you are. - What does
oc new-appdo?
It creates the objects needed to run an application from an image, a template or a Git repository, for exampleoc new-app https://github.com/sclorg/ruby-ex.git. - What is a Route?
An OpenShift object that exposes a Service at a hostname through the cluster's ingress router.oc expose service nginxcreates a basic HTTP route. - What is Source-to-Image (S2I)?
A build strategy that injects application source into a builder image and produces a runnable image without you writing a Dockerfile. - What is an ImageStream?
An object that tracks image tags and can trigger builds or deployments when the referenced image changes. - How do you see pod logs?
oc logs pod/backend, adding-cfor a specific container and-fto follow. - What is the web console used for?
Viewing and managing workloads, builds, Operators and monitoring from a browser, with separate developer and administrator views.
Intermediate FAQs
- What TLS termination types do Routes support?
Edge (TLS ends at the router), passthrough (encrypted traffic goes straight to the pod) and re-encrypt (the router terminates TLS and opens a new TLS connection to the pod). - Create an edge route for a service called frontend.
oc create route edge my-route --service=frontend. Add certificate and key flags if you are not using the router's default certificate. - What are SecurityContextConstraints?
Cluster objects that control what a pod may do: run as root, use host networking, mount host paths and so on. By default most workloads get the restricted-v2 SCC, which is why many images built to run as root fail on OpenShift. - A container image fails because it wants to run as root. What do you do?
Rebuild the image to run as an arbitrary non-root user with group-writable paths. Granting a more permissive SCC to the service account is possible, but it is a security trade-off you should justify. - DeploymentConfig or Deployment?
Deployment. Red Hat deprecated DeploymentConfig in OpenShift Container Platform 4.14 and says new features will not be added. Existing DeploymentConfigs should be migrated. - How do you roll back a bad rollout?
oc rollout undo deployment/myapp, and check progress withoc rollout status. - How do you trigger a build from local source?
oc start-build hello-world --from-dir=src/uploads the directory as the build input. - What is an Operator?
A controller that packages operational knowledge for an application, such as install, upgrade and backup, using custom resources. OpenShift installs and updates Operators through OperatorHub and the Operator Lifecycle Manager. - How are cluster components themselves managed?
By cluster Operators.oc get clusteroperatorsshows whether each one is available, progressing or degraded. - How do you debug a crashing pod?
Readoc logsandoc describe pod, check events, then useoc debug deploy/myappto start a copy of the pod with a shell for investigation.
Experienced FAQs
- How do you limit what a team can consume?
ResourceQuotas cap total CPU, memory and object counts per project. LimitRanges set default and maximum requests and limits per pod or container. - How do you isolate network traffic between projects?
Use NetworkPolicy objects to allow only required traffic. Start with a default deny for ingress in each project and add explicit allows. - How do you give a user rights in one project only?
Bind a role at project scope, for example withoc adm policy add-role-to-user edit alice -n team-a, instead of a cluster-wide role. - How do you add health checks?
Define readiness and liveness probes in the Deployment, or set them from the CLI withoc set probe. - How do upgrades work?
OpenShift 4 upgrades are managed by the Cluster Version Operator. Check the available updates, read the release notes, back up etcd, then upgrade in supported steps. - What do you back up?
etcd for cluster state, and application data separately through persistent volume snapshots or a backup Operator. - How do you run GitOps on OpenShift?
Red Hat offers OpenShift GitOps, based on Argo CD, installed as an Operator. Git holds the desired state and the controller keeps the cluster in sync. See our GitOps and Argo CD questions.
Scenario quick answers
- The route returns "Application is not available".
The router cannot reach a ready endpoint. Check that the Service selector matches pod labels, that pods are Ready, and that the route targets the right service and port. - A build fails pulling the base image.
Check the ImageStream reference, registry credentials (pull secret linked to the builder service account), and network egress to the registry. - Pods stay Pending.
Read the events: insufficient CPU or memory, a quota limit, an unbound PersistentVolumeClaim, or node selectors that match no node. - A cluster Operator reports Degraded.
Runoc describe clusteroperator <name>to read its conditions and message, then check the pods in that Operator's namespace.
How to use this sheet
Read each question, answer aloud in under thirty seconds, then compare. Where your answer was vague, run the command in a lab. A small lab cluster is enough for every command here. Interviewers notice when you name the object and the command without hesitation. They also notice when someone only knows Kubernetes and calls everything an Ingress, so practise the OpenShift words: project, route, SCC, image stream, Operator.
If you want structured labs on these topics, the OpenShift training course runs in our Kharadi, Pune classroom and as live online classes across India.
Commands to practise before the interview
oc login --username=myuser
oc new-project web-team-dev
oc new-app https://github.com/sclorg/ruby-ex.git
oc expose service ruby-ex
oc get route
oc rollout status deployment/ruby-ex
oc logs -f deployment/ruby-ex
oc debug deploy/ruby-ex
oc get clusteroperators
Run them in order in a lab and watch what each creates. oc new-app sets up a build from source when you give it a Git URL, so you will see a build pod before the application pod. oc expose turns the Service into a Route, and oc get route shows the hostname. If you can walk an interviewer through that sequence and explain each object it creates, you have covered a large share of beginner and intermediate questions.
Common mistakes candidates make
- Describing OpenShift only in Kubernetes terms and never mentioning Routes, SCCs or Projects.
- Recommending DeploymentConfig for new work, when Red Hat now recommends Deployments.
- Suggesting the anyuid SCC as the default fix for root containers without discussing the security cost.
- Forgetting that cluster components are Operators, so cluster health questions start with
oc get clusteroperators. - Giving long answers with no command. A short answer plus the command you would run is stronger.
Interviewers for OpenShift roles often come from a Red Hat Enterprise Linux background, so expect some Linux questions too: SELinux contexts, systemd units and firewall basics. Our RHEL guides and the OpenShift questions above work well together.
Where OpenShift questions usually come from
Most OpenShift interviews follow the job. Platform or administrator roles focus on installation, upgrades, cluster Operators, quotas, network policy, storage classes and backups. Developer-facing roles focus on builds, image streams, routes, Deployments, probes and getting an application from Git to a running pod. Many panels also add a few security questions about SCCs and role bindings, because these are where OpenShift differs most from plain Kubernetes and where misconfiguration causes real problems.
Read the job description and weight your revision accordingly. If it mentions "cluster administration" or "OpenShift platform", spend more time on the experienced section and on upgrade and backup procedures. If it mentions "application deployment" or "CI/CD on OpenShift", spend more time on builds, routes and rollouts. Either way, be ready to explain one OpenShift problem you solved, step by step, with the commands you used.
One last tip: when you do not know an answer, say how you would find it. "I would check the operator's conditions with oc describe and read the events" is a better answer than a guess, and interviewers for operations roles value that habit because it is exactly what the job needs during an outage. Calm, methodical answers count, even when you are unsure of the final fix.
Frequently asked questions
Is OpenShift just Kubernetes?
It is a Kubernetes distribution with extra objects and tooling, such as Routes, SCCs, builds, image streams and Operator-based lifecycle management.
Is DeploymentConfig still supported?
It still works, but Red Hat deprecated it in OpenShift Container Platform 4.14 and recommends Kubernetes Deployments for new work.
What are the Route TLS termination types?
Edge, passthrough and re-encrypt.
What is the difference between oc and kubectl?
oc supports kubectl commands and adds OpenShift features such as login, projects, builds and routes.
Why does my image fail on OpenShift but work on Kubernetes?
Usually because it expects to run as root, which the default restricted security constraints block.
What is OKD?
The community Kubernetes distribution that OpenShift is built from.
How do I check cluster health quickly?
Run oc get clusteroperators and oc get nodes and look for anything not available or not Ready.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0