50+ OpenShift Developer Interview Questions (2027)
52 OpenShift developer interview questions: S2I, BuildConfig, ImageStreams, Routes, Deployments, ConfigMaps, Tekton, Helm and debugging, with oc commands.
An OpenShift developer interview tests how you build, deploy and debug applications on the platform: Source-to-Image and BuildConfigs, ImageStreams, Deployments, Routes, ConfigMaps and Secrets, health probes, Helm or Kustomize, Tekton pipelines and Operators. These 52 questions are written from the developer side, with the oc commands you are expected to know.
OpenShift is Red Hat's Kubernetes-based platform, so developers are expected to know Kubernetes objects first. If you need that base, read our guide to the Kubernetes architecture components before this page. Answers here were checked against the OpenShift Container Platform 4.22 documentation sources and Red Hat's EX288 exam page.
This post is the application developer view. For cluster operation, see OpenShift administration questions; for the broad list, the 120-question master guide; for trouble tickets, scenario-based questions and advanced questions. Hands-on labs are available in our OpenShift training.
The developer exam objectives at a glance
Red Hat's EX288 page (Red Hat Certified Advanced Developer in Cloud-native Applications) describes a hands-on exam based on OpenShift Container Platform 4.22 with a time limit of 4 hours. The areas it lists map to this page as follows.
| EX288 objective area (Red Hat page) | Where it appears below |
|---|---|
| Projects, single and multi-container apps, health monitoring, internal registry | Questions 1 to 10 and 25 to 30 |
| Helm charts and Kustomize | Questions 39 to 41 |
| Image builds, build configurations, custom builders, publishing to the internal registry | Questions 11 to 24 |
| Image streams, ConfigMaps and Secrets, S2I, build hooks and triggers, templates | Questions 14 to 24 and 31 to 34 |
| OpenShift Pipelines (Tekton) and Operators | Questions 42 to 46 |
| Troubleshooting builds and deployments | Questions 47 to 52 |
Key takeaways
- Use
Deploymentobjects for new apps. Red Hat documentsDeploymentConfigas deprecated since OpenShift 4.14. - Source-to-Image injects application source into a builder image to produce a ready-to-run image. BuildConfigs, ImageStreams and triggers tie builds to code and base image changes.
- Routes expose services outside the cluster. Know edge, passthrough and reencrypt TLS termination.
- Configuration belongs in ConfigMaps and Secrets, injected as environment variables or files, never baked into images.
- The Pipeline build strategy is deprecated. Use OpenShift Pipelines, which is based on Tekton.
- For debugging, fluency with
oc logs,oc describe,oc debug,oc rshandoc get eventsmatters more than memorising YAML.
Platform and project basics (questions 1 to 10)
1. How does OpenShift differ from plain Kubernetes for a developer?
OpenShift adds developer-facing features on top of Kubernetes: Source-to-Image builds, ImageStreams, Routes, an integrated image registry, a web console with a developer view, and stricter default security through security context constraints.
2. What is a project?
A Kubernetes namespace with extra annotations and access controls. It isolates an application's resources and quotas. Create one with oc new-project.
3. What is the oc command line?
The OpenShift CLI. It includes the kubectl-style verbs and adds OpenShift commands such as new-app, start-build, expose and adm.
4. How do you deploy an app straight from a Git repository?
Run oc new-app <git-url>. OpenShift detects the language, selects a builder image or uses a Dockerfile, and creates the build, image stream, deployment and service.
oc new-project shop-dev
oc new-app https://git.example.com/team/shop.git --name=shop
oc logs -f buildconfig/shop
oc expose service/shop
oc get route shop
5. How do you deploy an existing container image?
Use oc new-app --image=<image> or import it into an image stream first. Then expose its service with a route if it needs outside traffic.
6. What are the main objects new-app creates?
A BuildConfig (for source builds), an ImageStream, a Deployment, and a Service. The Route is created separately with oc expose.
7. What is the difference between a Deployment and a DeploymentConfig?
Both describe the desired state of an application. Deployment is the Kubernetes object that uses replica sets. DeploymentConfig is the older OpenShift object that uses replication controllers. Red Hat says use Deployment unless you need a feature only DeploymentConfig provides.
8. Is DeploymentConfig removed?
No. As of OpenShift 4.14 DeploymentConfig is deprecated but still supported. It is not recommended for new installations, and only security-related and critical issues are fixed.
9. How do you scale an application?
Run oc scale deployment/shop --replicas=3 for a fixed count, or create a HorizontalPodAutoscaler for CPU or memory based scaling.
10. How do you control resource use per container?
Set requests and limits on the container. Requests drive scheduling, limits cap usage. A project quota or limit range can enforce defaults and maximums.
Builds, images and ImageStreams (questions 11 to 24)
11. What is Source-to-Image (S2I)?
A tool for building reproducible container images. It injects application source into a builder image and assembles a new image that is ready to run. S2I also supports incremental builds that reuse earlier dependencies.
12. What build strategies does OpenShift support?
Source (S2I), Docker (Containerfile based), Custom and Pipeline. The Pipeline strategy is deprecated in OpenShift 4 in favour of OpenShift Pipelines based on Tekton.
13. When would you choose a Docker strategy over S2I?
When you already own a Containerfile or Dockerfile with specific OS packages or layers that S2I builder images do not offer.
14. Why are custom builds restricted?
A custom build uses your own builder image for the whole build and runs with a high level of privilege. It is not available to users by default and should be granted only to people trusted with cluster administration permissions.
15. What is a BuildConfig?
An object that defines how to build an image: the source, the strategy, the output image stream tag and the triggers.
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata:
name: shop
spec:
source:
git:
uri: https://git.example.com/team/shop.git
strategy:
sourceStrategy:
from:
kind: ImageStreamTag
name: nodejs:latest
namespace: openshift
output:
to:
kind: ImageStreamTag
name: shop:latest
triggers:
- type: ConfigChange
- type: ImageChange
- type: GitHub
github:
secretReference:
name: shop-webhook-secret
16. What triggers can start a build?
Webhook, image change and configuration change triggers. Webhooks fire from your Git host, image change fires when the base image tag is updated, and configuration change fires when the BuildConfig is created or changed.
17. How do you start a build by hand and watch it?
oc start-build shop --follow starts a build and streams the log. oc get builds lists them and oc cancel-build stops one.
18. What is an ImageStream?
An OpenShift object that tracks images by tag without storing the image data itself. Builds and deployments can reference it, which lets OpenShift detect when a tag changes and react.
19. How do image stream triggers help?
A deployment or build can watch an image stream tag. When the tag points to a new image, OpenShift rolls out the new image or rebuilds dependent images, which keeps base image patches flowing.
20. How do you bring an external image into an image stream?
Use oc import-image or oc tag. Tagging an external image into a stream gives builds and deployments one stable reference.
21. What are build hooks?
The postCommit hook runs commands in a temporary container from the build output image after the last layer is committed and before the image is pushed. A non-zero exit fails the build, so it works as a quick test gate.
22. Can a build hook change the final image?
No. It runs in a temporary container and its changes do not persist, so it cannot alter the pushed image.
23. How do you push an image to the internal registry?
A BuildConfig with an ImageStreamTag output pushes there automatically. For manual pushes, log in with a token (oc whoami -t) and push to the registry route for your project.
24. How do you troubleshoot a failed build?
Read oc logs -f build/<name>, check that the source URL and secret are valid, confirm the builder image tag exists in the image stream, and check quota. Rebuild with oc start-build after the fix.
Deploy, configure and expose (questions 25 to 38)
25. What do liveness and readiness probes do?
A failing liveness probe restarts the container. A failing readiness probe removes the pod from service endpoints without restarting it. Add both for every production app.
oc set probe deployment/shop --readiness --get-url=http://:8080/healthz --initial-delay-seconds=5
oc set probe deployment/shop --liveness --get-url=http://:8080/healthz --period-seconds=10
26. What is a startup probe for?
Slow-starting applications. It delays liveness and readiness checks until the app has started, so a long boot is not mistaken for a failure.
27. How does a rolling update work?
The Deployment creates pods of the new version gradually while removing old ones, within limits set by max surge and max unavailable. Readiness probes decide when new pods may take traffic.
28. How do you roll back?
Run oc rollout undo deployment/shop to return to the previous revision, and oc rollout history to see revisions.
29. What is a Service?
A stable virtual IP and DNS name that load balances across the pods selected by labels. Services give routes and other pods something stable to talk to.
30. What is a Route?
An OpenShift object that exposes a service at a hostname outside the cluster through the router (Ingress Controller). It is the usual way to publish HTTP and HTTPS apps.
31. Explain edge, passthrough and reencrypt.
Edge terminates TLS at the router and sends plain traffic to the pod. Passthrough sends encrypted traffic straight to the pod, which handles TLS. Reencrypt terminates at the router and then opens a new TLS connection to the pod.
oc create route edge shop --service=shop --hostname=shop.apps.example.com
oc create route passthrough shop-tls --service=shop-tls
oc create route reencrypt shop-re --service=shop-tls --dest-ca-cert=ca.crt
32. Which load balancing algorithm do routes use by default?
The haproxy.router.openshift.io/balance annotation sets it. The default is source for TLS passthrough routes and random for all other routes.
33. How do you inject configuration into an app?
Create a ConfigMap for non-sensitive values and a Secret for sensitive ones, then inject them as environment variables or mount them as files.
oc create configmap shop-config --from-literal=LOG_LEVEL=info
oc create secret generic shop-db --from-literal=password='change-me'
oc set env deployment/shop --from=configmap/shop-config
oc set env deployment/shop --from=secret/shop-db --prefix=DB_
34. Are Secrets encrypted?
Secrets are base64 encoded in the API, which is not encryption. Cluster admins can enable etcd encryption, and you should restrict who can read Secrets with RBAC.
35. What are security context constraints (SCCs)?
Cluster policies that control what a pod may do, such as running privileged, using host paths or running as a particular UID. They are the OpenShift counterpart to pod security controls.
36. Why does a container image that runs as root fail on OpenShift?
The default restricted SCCs require the pod to run as a user in a pre-allocated UID range for the project, and restricted-v2 drops all capabilities. Build images that run as a non-root user and write only to writable paths.
37. What is persistent storage and how do developers request it?
A PersistentVolumeClaim asks for storage of a size and access mode, and a storage class provisions the volume. Mount the claim in the pod spec. Stateless apps do not need it.
38. How do you make an app configurable per environment?
Keep one image, vary ConfigMaps, Secrets and replica counts per project, and use Helm values or Kustomize overlays to manage the differences.
Templates, Helm, Kustomize, Pipelines and Operators (questions 39 to 46)
39. What is an OpenShift Template?
A parameterised set of objects processed with oc process and created with oc create. Templates can be JSON or YAML, hold several objects, and accept custom parameters.
40. What is Helm and when do you use it?
A package manager for Kubernetes. A chart bundles templates and default values, and you install it as a release with your own values. Use it for apps that ship as charts or need versioned releases.
41. What is Kustomize?
A way to customise YAML without templates, using a base and overlays that patch it per environment. It is built into oc and kubectl through the -k flag.
42. How do you choose between Helm and Kustomize?
Helm suits packaged, parameterised distribution and release history. Kustomize suits simple environment differences on plain YAML you already own. Many teams use both.
43. What is OpenShift Pipelines?
The CI/CD feature built on Tekton. Pipelines are made of tasks that run as pods, defined by Tekton custom resources such as Task, Pipeline, TaskRun and PipelineRun.
44. How are pipeline runs triggered?
Manually by creating a PipelineRun, or automatically from Git events using Tekton Triggers, which listen for webhooks and start runs.
45. What is an Operator?
Software that packages, deploys and manages an application using custom resources and a controller. Developers create application instances from installed Operators, for example a database, by applying a custom resource.
46. How does a developer use an installed Operator?
Create the Operator's custom resource in the project, from the web console or with YAML. The Operator then creates and manages the underlying pods, services and storage.
Troubleshooting and practical checks (questions 47 to 52)
47. A pod is in CrashLoopBackOff. What do you do?
Read the previous container's logs with oc logs --previous, describe the pod for exit codes and events, then check probes, environment variables, permissions and memory limits.
oc get events --sort-by=.lastTimestamp
oc describe pod <pod-name>
oc logs <pod-name> --previous
oc debug deployment/shop
oc rsh <pod-name>
oc start-build shop --follow
48. A pod is stuck in ImagePullBackOff.
Check the image name and tag, the image stream reference, and the pull secret. For internal images, confirm the project has permission to pull from the source namespace.
49. The route returns 503. Where do you look?
Confirm the service has endpoints (oc get endpoints), that selector labels match pod labels, that pods are ready and that the route points to the right service and port.
50. A deployment is Pending. What can cause it?
Insufficient CPU or memory on nodes, a quota limit in the project, an unbound PersistentVolumeClaim or a node selector with no match. oc describe pod shows the scheduler message.
51. The app works locally but fails on OpenShift. Likely reasons?
Running as root, writing to a read-only path, missing environment variables, wrong port binding or a service listening only on localhost. Use oc debug to start a copy with a shell.
52. How do you keep builds and deployments reproducible?
Pin base image tags, store BuildConfig and Deployment manifests in Git, keep configuration out of images and let triggers or a pipeline apply changes instead of manual edits.
Frequently asked questions
What is the difference between OpenShift and Kubernetes for developers?
OpenShift is Kubernetes plus developer features such as Source-to-Image, ImageStreams, Routes, an integrated registry, a developer console and stricter default security through security context constraints.
Is DeploymentConfig deprecated?
Yes. Red Hat documents DeploymentConfig as deprecated as of OpenShift 4.14. It is still supported but not recommended for new installations, so use Deployment.
What is Source-to-Image?
A tool that injects application source into a builder image and assembles a ready-to-run container image, with support for incremental builds.
What are the three TLS termination types for routes?
Edge, passthrough and reencrypt. Edge terminates at the router, passthrough lets the pod terminate TLS, and reencrypt terminates at the router and encrypts again to the pod.
Which build strategy is deprecated?
The Pipeline build strategy is deprecated in OpenShift 4. Red Hat points to OpenShift Pipelines based on Tekton as the replacement.
What does the EX288 exam cover?
Red Hat describes EX288 as a hands-on exam on OpenShift Container Platform 4.22 with a 4 hour time limit. Objectives include builds, image streams, S2I, templates, Helm, Kustomize, pipelines and Operators.
How should I prepare for an OpenShift developer interview?
Deploy an app with oc new-app, add a BuildConfig with triggers, a route with TLS, a ConfigMap and Secret, probes and a Tekton pipeline, then break each one on purpose and fix it.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0