OpenShift Developer Interview Questions [2025]

Application Deployment

1. What is OpenShift’s role in application deployment?

• OpenShift is a Kubernetes-based platform.
• Automates containerized app deployments.
• Uses BuildConfigs for CI/CD.
• Supports Source-to-Image for builds.
• Ensures secure networking via routes.
• Simplifies developer workflows.

OpenShift streamlines deployments for interviews.

2. Why deploy applications on OpenShift?

OpenShift simplifies container management with integrated CI/CD, Source-to-Image (S2I), and routes for external access. It offers RBAC for security and integrates with Prometheus for monitoring. Compared to vanilla Kubernetes, it reduces setup complexity. Validate deployments in a test project to demonstrate expertise for certification interviews.

3. When do you use oc new-app for deployment?

• Use for quick app deployments.
• Supports Git repositories or Docker images.
• Run: oc new-app my-repo.git.
• Validate in test project.
• Monitor with Prometheus.
• Ensure route accessibility.

Rapid app setup is needed. This shows deployment skills.

4. Where do you configure deployment strategies?

Configure deployment strategies in DeploymentConfig via oc edit dc/my-app. Options include Rolling or Recreate strategies. Validate in a test project to ensure zero-downtime updates. Monitor with oc describe dc/my-app to demonstrate deployment expertise for interviews.

5. Who creates application templates in OpenShift?

• Developers create templates for reusability.
• Store in OpenShift Catalog.
• Use oc create -f template.yaml.
• Validate in test project.
• Monitor deployment status.
• Collaborate with DevOps teams.

This role showcases template skills for interviews.

6. Which tools support OpenShift deployments?

OpenShift integrates with Ansible for configuration, Jenkins for CI/CD, and Helm for Kubernetes packages. Use oc new-app for quick setups.

• Configure Ansible playbooks for apps.
• Use Jenkins for pipeline automation.
• Validate in test project.
• Monitor with Prometheus.

This enhances deployment for certification.

7. How do you deploy a multi-container app?

• Define pod with multiple containers in YAML.
• Use oc apply -f multi-container.yaml.
• Configure shared volumes if needed.
• Validate in test project.
• Monitor with oc describe pod.
• Ensure network connectivity.

An app needs multiple services. This shows deployment skills.

8. What is a DeploymentConfig in OpenShift?

DeploymentConfig is an OpenShift-specific resource that manages application deployments, supporting strategies like Rolling or Recreate. It triggers updates via image changes or config updates. Compared to Kubernetes Deployments, it offers built-in triggers. Validate in a test project to show deployment expertise for interviews.

9. Why use templates for app deployment?

• Templates ensure consistent deployments.
• Define reusable app configurations.
• Store in OpenShift Catalog.
• Validate in test project.
• Monitor with Prometheus.
• Simplify team workflows.

Teams need standardized setups. This ensures deployment consistency.

10. When do you use image streams?

Use image streams to manage container images in OpenShift, tracking updates and triggering deployments. Configure via oc create imagestream my-app. Validate in a test project to ensure automatic updates. Monitor with oc describe is/my-app to show image management skills for interviews.

11. Where do you store application configurations?

• Use ConfigMaps for non-sensitive data.
• Store secrets in Secrets for sensitive data.
• Apply with oc create configmap my-config.
• Validate in test project.
• Monitor with oc describe cm.
• Ensure secure access.

Apps need configurations. This supports deployment skills.

12. Who manages application rollbacks?

A deployment fails. The developer initiates rollbacks using oc rollback dc/my-app. They collaborate with DevOps for validation.

• Check history with oc rollout history.
• Validate in test project.
• Monitor with Prometheus.
• Ensure rollback stability.

This shows deployment expertise for interviews.

13. Which resources define an application?

• DeploymentConfig for deployment logic.
• Service for internal networking.
• Route for external access.
• Validate in test project.
• Monitor with Prometheus.
• Use ConfigMaps for settings.

This demonstrates app setup skills.

14. How do you handle deployment failures?

A deployment fails. Check logs with oc logs dc/my-app. Verify image and config with oc describe dc/my-app. Revert with oc rollback dc/my-app. Validate in a test project to show troubleshooting skills for interviews.

15. What is the role of OpenShift’s web console?

• Provides a UI for app management.
• Visualizes deployments and resources.
• Supports creating routes and services.
• Validate in test project.
• Monitor with console dashboards.
• Simplifies developer tasks.

Developers need UI access. This supports interviews.

16. Why secure application configurations?

Configs expose sensitive data. Use Secrets for API keys and ConfigMaps for non-sensitive data. Apply with oc create secret generic my-secret. Restrict access via RBAC. Validate in a test project to show security skills for interviews.

17. How do you optimize application deployments?

• Use Rolling strategy for zero downtime.
• Configure triggers for image updates.
• Validate in test project.
• Monitor with Prometheus.
• Reduce image sizes.
• Ensure network efficiency.

Deployments are slow. This shows optimization skills.

18. Which strategies ensure deployment reliability?

Deployments fail intermittently. Use health checks in DeploymentConfig and validate image streams. Monitor with Prometheus for trends.

• Configure liveness/readiness probes.
• Validate in test project.
• Monitor deployment status.
• Ensure stable networking.

This ensures reliable deployments for interviews.

CI/CD and BuildConfigs

19. What is a BuildConfig in OpenShift?

• Defines build processes for apps.
• Supports Source-to-Image and Docker builds.
• Uses triggers for automation.
• Integrates with Git repositories.
• Validates in test project.
• Monitors with Prometheus.

BuildConfigs streamline CI/CD for interviews.

20. Why use Source-to-Image (S2I) for builds?

S2I automates image creation from source code, reducing manual Docker file creation. It uses builder images to compile code and produce deployable images. Compared to manual builds, it simplifies workflows. Validate in a test project to show CI/CD skills for certification interviews.

21. When do you configure build triggers?

• Set triggers for Git commits.
• Configure via oc set triggers bc/my-build.
• Support CI/CD automation.
• Validate in test project.
• Monitor with Prometheus.
• Ensure pipeline efficiency.

Builds need automation. This shows CI/CD expertise.

22. Where do you store build artifacts?

Store artifacts in OpenShift’s integrated registry, accessible via oc registry login. Push images with oc tag. Validate in a test project to ensure availability. Monitor with oc describe is/my-image to demonstrate CI/CD skills for interviews.

23. Who designs CI/CD pipelines in OpenShift?

• Developers design pipelines with DevOps.
• Use BuildConfigs and Jenkins/Tekton.
• Configure via oc create pipeline.
• Validate in test project.
• Monitor with Prometheus.
• Ensure team alignment.

Teams need pipelines. This shows collaboration skills.

24. Which tools enhance OpenShift CI/CD?

Pipelines need automation. Use Tekton for Kubernetes-native pipelines and Jenkins for traditional CI/CD. Integrate with Git.

• Configure Tekton pipelines.
• Validate in test project.
• Monitor with Prometheus.
• Automate with triggers.

This shows CI/CD expertise for interviews.

25. How do you troubleshoot a failing build?

• Check logs with oc logs bc/my-build.
• Verify BuildConfig syntax.
• Inspect source repository access.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic scripts.

A build fails. This shows troubleshooting skills.

26. What causes build timeouts?

Builds fail due to timeouts. Increase timeout in BuildConfig with oc edit bc/my-build. Validate in test project and monitor with Prometheus to show CI/CD skills for interviews.

27. Why do builds fail to access repositories?

• Missing Git credentials in BuildConfig.
• Add secrets with oc create secret.
• Verify repository URL.
• Validate in test project.
• Monitor with Prometheus.
• Ensure network access.

Builds cannot fetch code. This shows troubleshooting expertise.

28. When do you use Docker builds?

Use Docker builds for custom images when S2I is insufficient. Define Dockerfile in the repository and configure BuildConfig. Validate in a test project to ensure image creation. Monitor with oc describe bc/my-build to show build skills for interviews.

29. Where do you debug build failures?

• Use oc logs bc/my-build for errors.
• Check BuildConfig triggers.
• Verify source repository access.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic tools.

Builds fail unexpectedly. This shows debugging skills.

30. Who resolves pipeline failures?

A pipeline stalls. The developer debugs with oc logs pipeline/my-pipeline and collaborates with DevOps for fixes. Monitor with Prometheus.

• Validate in test project.
• Check pipeline stages.
• Ensure resource availability.
• Monitor execution.

This shows teamwork for interviews.

31. Which metrics track pipeline health?

• Monitor build success rate in Prometheus.
• Track build duration.
• Analyze failures with scripts.
• Validate in test project.
• Monitor pipeline efficiency.
• Automate alerts.

This demonstrates observability skills.

32. How do you automate pipeline triggers?

Pipelines need automation. Configure triggers in BuildConfig with oc set triggers bc/my-build. Integrate with Git webhooks. Validate in a test project to show CI/CD skills for interviews.

33. What causes pipeline resource exhaustion?

• Insufficient CPU/memory for builds.
• Increase limits in BuildConfig YAML.
• Check with oc describe bc/my-build.
• Validate in test project.
• Monitor with Prometheus.
• Optimize resource usage.

Builds fail due to resources. This shows troubleshooting skills.

34. Why use Tekton for CI/CD?

Tekton provides Kubernetes-native pipelines, integrating seamlessly with OpenShift. It supports reusable tasks and pipelines. Configure via oc apply -f pipeline.yaml and validate in a test project. Monitor with Prometheus to show CI/CD expertise for interviews.

35. When do you integrate Jenkins with OpenShift?

• Use for legacy pipeline compatibility.
• Deploy Jenkins via OpenShift template.
• Configure with oc new-app jenkins.
• Validate in test project.
• Monitor with Prometheus.
• Ensure pipeline automation.

Legacy CI/CD is needed. This shows integration skills.

Networking and Routes

36. What is a Route in OpenShift?

• Exposes services to external traffic.
• Uses HAProxy for load balancing.
• Configure with oc expose svc/my-service.
• Supports TLS termination.
• Validates in test project.
• Monitors with Prometheus.

Routes ensure external access for interviews.

37. Why use secure routes?

• Protect traffic with TLS encryption.
• Configure edge or re-encrypt termination.
• Apply with oc create route edge.
• Validate in test project.
• Monitor with Prometheus.
• Ensure security compliance.

Apps need secure access. This shows security skills.

38. When do you configure network policies?

Configure network policies to restrict pod communication, defined via oc apply -f policy.yaml. Validate in a test project to ensure secure networking. Monitor with Prometheus to demonstrate networking skills for interviews.

39. Where do you manage route configurations?

• Use oc edit route/my-route for settings.
• Configure in OpenShift Web Console.
• Adjust TLS or path-based routing.
• Validate in test project.
• Monitor with Prometheus.
• Ensure route accessibility.

Routes need customization. This shows networking expertise.

40. Who manages route access control?

The developer configures RBAC for routes, ensuring only authorized users access them. Apply with oc adm policy add-role-to-user. Validate in a test project and monitor with Prometheus to show security skills for interviews.

41. Which tools troubleshoot route connectivity?

• Use oc describe route/my-route for errors.
• Run curl for external access tests.
• Analyze with networking tools like tcpdump.
• Validate in test project.
• Monitor with Prometheus.
• Automate diagnostics.

Routes are inaccessible. This shows troubleshooting skills.

42. How do you secure a route with TLS?

A route exposes sensitive data. Configure edge termination with oc create route edge --cert my-cert.pem. Validate in a test project.

• Monitor with Prometheus.
• Ensure certificate validity.
• Check route accessibility.
• Update firewall rules.

This shows secure networking for interviews.

43. What causes route timeouts?

• Misconfigured timeout settings in route.
• Check with oc describe route/my-route.
• Adjust timeout in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure service availability.

Users report timeouts. This shows troubleshooting skills.

44. Why does a service lack external access?

A service is unreachable. The route is missing or misconfigured. Create with oc expose svc/my-service. Verify service selector. Validate in a test project to show networking skills for interviews.

45. When do you use path-based routing?

• Use for multiple apps on one domain.
• Configure in route YAML with path.
• Apply with oc apply -f route.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure routing accuracy.

Apps share a domain. This shows routing expertise.

46. Where do you monitor route traffic?

Use Prometheus to monitor route metrics, configured via Cluster Monitoring Operator. Analyze with Grafana dashboards. Validate in test project to demonstrate networking skills for interviews.

47. Who resolves route configuration errors?

• Developer fixes route settings.
• Check with oc describe route/my-route.
• Update YAML for corrections.
• Validate in test project.
• Monitor with Prometheus.
• Collaborate with DevOps.

Routes fail to route traffic. This shows troubleshooting expertise.

48. Which steps secure a route with RBAC?

Unauthorized route access occurs. Configure RBAC with oc adm policy add-role-to-user view user1 -n my-project. Validate in a test project.

• Monitor with Prometheus.
• Ensure least privilege.
• Check audit logs.
• Validate access controls.

This shows security skills for interviews.

49. How do you handle route performance issues?

• Check Prometheus for latency metrics.
• Adjust route timeout settings.
• Optimize backend service performance.
• Validate in test project.
• Monitor with Grafana.
• Scale pods if needed.

Routes are slow. This shows performance expertise.

50. What causes a route to fail?

A route is inaccessible. Check route configuration with oc describe route/my-route. Verify service selector and backend health. Validate in a test project and monitor with Prometheus to show networking skills for interviews.

51. Why use Network Policies in OpenShift?

• Restrict pod-to-pod communication.
• Define rules in networkpolicy.yaml.
• Apply with oc apply -f policy.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Enhance app security.

Apps need isolation. This shows networking expertise.

52. When do you configure load balancing for routes?

Use load balancing for high-traffic apps, configured in route YAML with round-robin or leastconn. Validate in a test project. Monitor with Prometheus to demonstrate load balancing skills for interviews.

Persistent Storage

53. What is a Persistent Volume Claim (PVC)?

• Requests storage for stateful apps.
• Defines size and access mode.
• Binds to Persistent Volumes (PVs).
• Apply with oc apply -f pvc.yaml.
• Validates in test project.
• Monitors with Prometheus.

PVCs ensure data persistence for interviews.

54. Why does a pod fail to mount a PVC?

A pod cannot access storage. The PVC is misconfigured or PV is unavailable. Check with oc describe pvc/my-pvc. Verify storage class. Validate in a test project to show storage skills for interviews.

55. When do you use dynamic provisioning?

• Use for automatic PV creation.
• Configure storage class in PVC.
• Apply with oc apply -f pvc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure storage scalability.

Storage needs automation. This shows storage expertise.

56. Where do you configure storage classes?

Define storage classes in YAML for dynamic provisioning. Apply with oc apply -f storageclass.yaml. Validate in test project to show storage management skills for interviews.

57. Who manages PVC configurations?

• Developers configure PVCs for apps.
• Collaborate with admins for PVs.
• Apply with oc apply -f pvc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data persistence.

Apps need storage. This shows storage expertise.

58. Which storage types support stateful apps?

A database needs storage. Use block storage (e.g., Ceph RBD) or NFS for stateful apps. Configure via storage class. Validate in a test project to show storage skills for interviews.

59. How do you troubleshoot storage mounting issues?

• Check oc describe pvc/my-pvc for errors.
• Verify storage class and PV availability.
• Inspect pod events with oc describe pod.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic scripts.

Pods cannot mount storage. This shows troubleshooting skills.

60. What causes PVC binding failures?

A PVC fails to bind. Check storage class and PV availability with oc describe pvc/my-pvc. Ensure sufficient capacity. Validate in a test project and monitor with Prometheus to show storage skills for interviews.

61. Why use volume snapshots?

• Create backups for stateful apps.
• Configure via snapshot YAML.
• Apply with oc apply -f snapshot.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data recovery.

Data needs backups. This shows storage expertise.

62. When do you expand PVCs?

Expand PVCs when storage runs low, using oc edit pvc/my-pvc to increase spec.resources.requests.storage. Validate in a test project to show storage management skills for interviews.

63. Where do you store volume snapshots?

• Store snapshots in storage backend.
• Configure via storage class.
• Apply with oc apply -f snapshot.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure snapshot availability.

Backups need storage. This shows storage skills.

64. Who resolves PVC mounting issues?

The developer debugs with oc describe pvc/my-pvc and collaborates with admins for PV issues. Validate in a test project. Monitor with Prometheus to show storage troubleshooting skills for interviews.

65. Which tools manage persistent storage?

• Use storage classes for dynamic provisioning.
• Configure with oc apply -f storageclass.yaml.
• Integrate with Ceph or NFS.
• Validate in test project.
• Monitor with Prometheus.
• Automate storage setup.

Storage needs management. This shows storage expertise.

66. How do you automate storage provisioning?

Storage needs automation. Use storage classes for dynamic provisioning and integrate with cloud providers like AWS EBS.

• Validate in test project.
• Monitor with Prometheus.
• Ensure storage scalability.
• Apply with oc apply.

This shows automation skills for interviews.

67. What causes storage performance issues?

• Low IOPS in storage backend.
• Check with oc describe pvc/my-pvc.
• Upgrade storage class performance.
• Validate in test project.
• Monitor with Prometheus.
• Optimize volume settings.

Storage is slow. This shows troubleshooting skills.

68. Why does a pod lose data?

Data disappears after pod restart. The PVC is not mounted or uses ephemeral storage. Verify with oc describe pod/my-pod. Configure PVC in YAML. Validate in a test project to show storage skills for interviews.

69. When do you use StatefulSets?

• Use for stateful apps like databases.
• Configure with oc apply -f statefulset.yaml.
• Ensure stable pod identities.
• Validate in test project.
• Monitor with Prometheus.
• Support data persistence.

Databases need Kubernetes. This shows application expertise.

Scaling and Performance

70. What is a Horizontal Pod Autoscaler (HPA)?

• Scales pods based on metrics.
• Configure with oc autoscale dc/my-app.
• Uses CPU/memory thresholds.
• Validate in test project.
• Monitor with Prometheus.
• Ensures performance scalability.

HPAs optimize performance for interviews.

71. Why does an app fail to scale?

• Missing HPA configuration.
• Check with oc describe hpa/my-app.
• Verify resource limits in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Adjust scaling thresholds.

App cannot handle load. This shows scaling expertise.

72. When do you use manual scaling?

• Use for predictable workloads.
• Configure with oc scale dc/my-app --replicas=3.
• Validate in test project.
• Monitor with Prometheus.
• Ensure resource availability.
• Support stable performance.

Workloads need fixed replicas. This shows scaling skills.

73. Where do you configure scaling policies?

• Define HPA in YAML with oc apply.
• Configure in OpenShift Web Console.
• Set CPU/memory thresholds.
• Validate in test project.
• Monitor with Prometheus.
• Ensure policy accuracy.

Apps need dynamic scaling. This shows performance expertise.

74. Who manages app scaling?

• Developers configure HPA or manual scaling.
• Collaborate with DevOps for resources.
• Apply with oc autoscale dc/my-app.
• Validate in test project.
• Monitor with Prometheus.
• Ensure performance stability.

Apps need scaling. This shows collaboration skills.

75. Which metrics drive autoscaling?

• Use CPU/memory in HPA YAML.
• Configure custom metrics with Prometheus.
• Apply with oc apply -f hpa.yaml.
• Validate in test project.
• Monitor with Grafana.
• Optimize scaling triggers.

Apps need dynamic scaling. This shows performance expertise.

76. How do you handle resource contention?

Pods compete for CPU. Adjust resource limits in DeploymentConfig with oc edit dc/my-app. Monitor with Prometheus.

• Validate in test project.
• Set resource limits in YAML.
• Ensure performance stability.
• Monitor resource usage.

This shows resource management for interviews.

77. What causes slow application performance?

• Insufficient resource limits in pods.
• Check with oc describe pod/my-pod.
• Optimize code or scale pods.
• Validate in test project.
• Monitor with Prometheus.
• Adjust network settings.

Users report delays. This shows troubleshooting skills.

78. Why use resource limits?

• Prevent resource overuse by pods.
• Configure in DeploymentConfig YAML.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure cluster stability.

Pods consume excess resources. This shows performance expertise.

79. When do you scale pods manually?

• Use for fixed workload requirements.
• Run oc scale dc/my-app --replicas=3.
• Validate in test project.
• Monitor with Prometheus.
• Ensure resource availability.
• Support predictable performance.

Workloads need stability. This shows scaling skills.

80. Where do you monitor scaling metrics?

• Use Prometheus for pod metrics.
• Configure via Cluster Monitoring Operator.
• Visualize with Grafana dashboards.
• Validate in test project.
• Monitor with alerts.
• Ensure performance visibility.

Scaling needs monitoring. This shows observability skills.

81. Who resolves scaling failures?

• Developer debugs HPA with oc describe hpa.
• Check resource limits in YAML.
• Collaborate with DevOps for fixes.
• Validate in test project.
• Monitor with Prometheus.
• Ensure scaling reliability.

Scaling fails. This shows troubleshooting expertise.

82. Which steps optimize pod performance?

• Set resource limits in DeploymentConfig.
• Optimize container images.
• Configure HPA for dynamic scaling.
• Validate in test project.
• Monitor with Prometheus.
• Reduce network latency.

Pods are slow. This shows performance skills.

83. How do you configure HPA for custom metrics?

Apps need custom scaling. Configure HPA with Prometheus metrics via oc apply -f hpa.yaml. Validate in a test project to show scaling skills for interviews.

84. What causes pod resource exhaustion?

• Missing resource limits in YAML.
• Check with oc describe pod/my-pod.
• Adjust limits with oc edit dc.
• Validate in test project.
• Monitor with Prometheus.
• Scale pods if needed.

Pods crash due to resources. This shows troubleshooting skills.

85. Why does an HPA fail to scale?

• Incorrect metric thresholds in HPA.
• Check with oc describe hpa/my-app.
• Verify Prometheus integration.
• Validate in test project.
• Monitor with Grafana.
• Adjust scaling policies.

Scaling does not occur. This shows scaling expertise.

Debugging and Monitoring

86. What is Prometheus in OpenShift?

• Monitors cluster and app metrics.
• Integrated via Cluster Monitoring Operator.
• Visualizes with Grafana dashboards.
• Validates in test project.
• Sets alerts for issues.
• Ensures observability.

Prometheus enhances monitoring for interviews.

87. Why do pods fail with CrashLoopBackOff?

• App errors or misconfigurations cause failures.
• Check logs with oc logs my-pod.
• Verify container image settings.
• Validate in test project.
• Monitor with Prometheus.
• Fix code or config.

Pods keep crashing. This shows debugging skills.

88. When do you use oc debug?

Use oc debug pod/my-pod to access a pod’s shell for troubleshooting. Validate in a test project to diagnose issues. Monitor with Prometheus to show debugging skills for interviews.

89. Where do you view application logs?

• Use oc logs my-pod for pod logs.
• Access via OpenShift Web Console.
• Integrate with EFK stack.
• Validate in test project.
• Monitor with Prometheus.
• Ensure log availability.

Logs are needed for debugging. This shows logging expertise.

90. Who debugs application failures?

• Developers debug with oc logs.
• Collaborate with DevOps for cluster issues.
• Use oc describe pod for events.
• Validate in test project.
• Monitor with Prometheus.
• Fix code or configs.

Apps fail unexpectedly. This shows troubleshooting expertise.

91. Which tools enhance OpenShift monitoring?

• Use Prometheus for metric collection.
• Integrate Grafana for visualization.
• Configure EFK for logging.
• Validate in test project.
• Monitor with alerts.
• Automate metric collection.

Visibility is needed. This shows observability skills.

92. How do you handle high latency in apps?

Users report slow responses. Check Prometheus for latency metrics. Optimize code or scale pods with oc scale dc/my-app. Validate in a test project to show performance troubleshooting skills for interviews.

93. What causes missing logs in OpenShift?

Logs are unavailable. Check EFK stack configuration and pod logging settings. Verify with oc describe pod/my-pod. Configure log forwarding. Validate in a test project and monitor with Prometheus to show logging skills for interviews.

94. Why use liveness probes?

• Ensure pods are running correctly.
• Configure in DeploymentConfig YAML.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Prevent app failures.

Pods need health checks. This shows reliability expertise.

95. When do you use readiness probes?

Use readiness probes to ensure pods are ready to serve traffic, configured in DeploymentConfig YAML. Validate in a test project to prevent downtime. Monitor with Prometheus to show reliability skills for interviews.

96. Where do you analyze performance issues?

Use Prometheus for metrics and Grafana for visualization. Check pod performance with oc adm top pod. Validate in test project to show performance troubleshooting skills for interviews.

97. Who monitors application alerts?

• Developers set Prometheus alerts.
• Configure via Cluster Monitoring Operator.
• Integrate with PagerDuty for notifications.
• Validate in test project.
• Monitor with Grafana.
• Ensure alert reliability.

Alerts indicate issues. This shows monitoring expertise.

98. Which steps fix pod crashes?

Pods crash repeatedly. Check logs with oc logs my-pod. Verify resource limits and app code. Validate in a test project to show debugging skills for interviews.

99. How do you implement zero-downtime deployments?

• Use Rolling strategy in DeploymentConfig.
• Configure maxSurge and maxUnavailable.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure network stability.

Deployments cause outages. This shows deployment expertise.

100. What causes high CPU usage in pods?

Pods consume excessive CPU. Check with oc adm top pod. Adjust resource limits in DeploymentConfig. Validate in a test project and monitor with Prometheus to show performance skills for interviews.

101. Why integrate Prometheus with OpenShift?

• Provides detailed app metrics.
• Configure via Cluster Monitoring Operator.
• Visualize with Grafana dashboards.
• Validate in test project.
• Monitor with alerts.
• Enhance observability.

Metrics are needed. This shows monitoring expertise.

102. When do you use log-based alerts?

Use log-based alerts in EFK stack to track errors. Configure in Prometheus with oc apply -f alert.yaml. Validate in a test project to show observability skills for interviews.

103. Where do you debug pod network issues?

• Use oc describe pod/my-pod for errors.
• Check network policies.
• Run curl for connectivity tests.
• Validate in test project.
• Monitor with Prometheus.
• Use network diagnostics.

Pods cannot communicate. This shows networking expertise.