Why this topic matters in interviews
OpenShift is Kubernetes-based, but interviewers usually expect more than generic Kubernetes knowledge. They test enterprise platform operations: Projects, Routes, Operators, SCC/RBAC, deployments, image handling, GitOps, observability, upgrades, troubleshooting and production controls.
15 interview questions to prepare
Cover enterprise features such as Projects, Routes, integrated authentication, Operators, SCC, registry/build capabilities, developer workflows, cluster monitoring, console experience and opinionated security defaults.
Explain that a Route exposes services externally through OpenShift router capabilities. Discuss edge, passthrough and re-encrypt TLS, hostnames, service mapping and troubleshooting route/service/endpoint checks.
SCCs control pod permissions such as privileged mode, host access, user IDs, volumes and security settings. A production answer should include RBAC binding, service accounts and least privilege.
Operators automate installation, upgrades and lifecycle management of complex software. Use examples like GitOps, service mesh, monitoring, logging, databases and platform add-ons.
Check events, logs, previous logs, probes, ConfigMaps, Secrets, image version, resource limits, SCC/RBAC errors, node pressure and recent deployment changes.
Validate route host, TLS mode, service, service port, endpoints, pod readiness, router pods, DNS, network policy and application logs.
OpenShift GitOps provides declarative workflows with Argo CD. Explain desired state in Git, sync, drift detection, rollback and app-of-apps patterns.
Check image reference, registry access, pull secrets, service account, network connectivity, image tag existence, image policy and internal registry permissions.
Discuss Deployment for stateless workloads, DeploymentConfig as OpenShift-specific workflow object, and StatefulSet for stable identity/persistent storage.
Cover multi-node control plane, worker distribution, infra nodes, ingress/router availability, storage, monitoring, logging, backup, etcd protection and upgrades.
Inspect pod events, service account, SCC bindings and container securityContext. Avoid broad privileged access; create least-privilege patterns.
Discuss platform monitoring, Prometheus metrics, alerts, pod logs, events, dashboards, probes and SLO-style workload health.
Explain traffic management, mTLS, observability, tracing, policy and microservices communication control.
Review cluster version, Operator compatibility, deprecated APIs, node health, backups, monitoring, capacity, maintenance window, release notes and rollback plan.
A senior engineer explains production trade-offs: security, governance, failure modes, automation, GitOps, observability, upgrades, capacity and incident response.