Scenario-Based OpenShift Interview Questions with Answers [2025]

Application Deployment

1. What causes a pod to crash repeatedly?

• Misconfigured container image in DeploymentConfig.
• Check logs with oc logs my-pod.
• Verify resource limits in YAML.
• Inspect pod events with oc describe pod.
• Monitor with Prometheus.
• Fix app code or config.

Pods keep restarting, requiring detailed debugging for interviews.

2. Why does a deployment fail to update?

An image update fails due to a missing image stream trigger. Configure with oc set triggers dc/my-app --from-image. Validate in a test project and monitor with Prometheus to resolve deployment issues.

3. When does a pod fail to start?

• Missing ConfigMap or Secret.
• Check with oc describe pod/my-pod.
• Configure with oc set env dc/my-app.
• Validate in test project.
• Monitor with Prometheus.
• Ensure resource availability.

Pods cannot initialize, requiring configuration fixes.

4. Where do you check for deployment errors?

Check deployment errors in pod logs using oc logs dc/my-app or events with oc describe dc/my-app. Validate in a test project to identify issues. Monitor with Prometheus to ensure deployment stability.

5. Who resolves application crashes?

• Developers debug app code issues.
• Admins check cluster resources.
• Use oc debug pod/my-pod for inspection.
• Validate in test project.
• Monitor with Prometheus.
• Collaborate for fixes.

Apps crash in production, requiring teamwork to resolve.

6. Which resources cause deployment bottlenecks?

High CPU or memory usage slows deployments. Check with oc adm top pod and adjust limits in DeploymentConfig YAML.

• Validate in test project.
• Monitor with Prometheus.
• Optimize resource allocation.
• Scale pods if needed.

Bottlenecks impact production, requiring resource tuning.

7. How do you fix a failed deployment rollout?

• Rollback with oc rollback dc/my-app.
• Check logs with oc logs dc/my-app.
• Verify image stream triggers.
• Validate in test project.
• Monitor with Prometheus.
• Fix YAML configuration.

Rollouts fail, requiring quick resolution to restore service.

8. What prevents an app from scaling?

Scaling fails due to insufficient cluster resources. Check with oc adm top nodes and configure HorizontalPodAutoscaler with oc autoscale dc/my-app. Validate in a test project to ensure scalability.

9. Why does an app return 503 errors?

• Readiness probe fails in pod.
• Check with oc describe pod/my-pod.
• Update probe in DeploymentConfig YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure service availability.

Users face service errors, requiring probe adjustments.

10. When does an app fail to access Secrets?

Secrets are inaccessible due to incorrect RBAC settings. Configure with oc adm policy add-role-to-user view user1 -n my-project. Validate in a test project for secure access. Monitor with audit logs to resolve access issues.

11. Where do you debug pod startup issues?

• Use oc describe pod/my-pod for events.
• Check logs with oc logs my-pod.
• Verify RBAC settings.
• Validate in test project.
• Monitor with Prometheus.
• Fix pod configuration.

Pods fail to start, requiring detailed diagnostics.

12. Who fixes app configuration errors?

Developers correct app YAML misconfigurations using oc edit dc/my-app and collaborate with admins for cluster issues.

• Validate in test project.
• Monitor with Prometheus.
• Check ConfigMap or Secret.
• Ensure app stability.

Apps fail due to configs, requiring teamwork to fix.

13. Which tools diagnose app performance issues?

• Use Prometheus for latency metrics.
• Run oc adm top pod for usage.
• Integrate with Grafana dashboards.
• Validate in test project.
• Monitor with alerts.
• Optimize pod resources.

Apps are slow, requiring performance diagnostics.

14. How do you resolve pod CrashLoopBackOff?

Pods crash repeatedly due to app errors. Debug with oc logs my-pod and oc debug pod/my-pod. Update DeploymentConfig YAML to fix code or resources. Validate in a test project to restore stability.

15. What causes app downtime during deployment?

• Incorrect Rolling strategy settings.
• Configure maxSurge in DeploymentConfig.
• Check with oc describe dc/my-app.
• Validate in test project.
• Monitor with Prometheus.
• Ensure zero-downtime updates.

Deployments cause outages, requiring strategy adjustments.

16. Why does an app fail health checks?

Liveness probes fail due to incorrect thresholds. Update probe settings in DeploymentConfig YAML with oc edit dc/my-app. Validate in a test project to ensure reliability. Monitor with Prometheus to resolve health issues.

17. How do you automate app scaling?

• Configure HorizontalPodAutoscaler with oc autoscale.
• Set CPU thresholds in YAML.
• Validate in test project.
• Monitor with Prometheus metrics.
• Ensure resource efficiency.
• Check scaling events.

High traffic requires dynamic scaling to maintain performance.

18. Which steps fix app memory leaks?

Memory leaks cause pod restarts. Check with oc adm top pod and set memory limits in DeploymentConfig YAML.

• Validate in test project.
• Monitor with Prometheus.
• Optimize app code.
• Scale pods if needed.

Leaks impact performance, requiring resource tuning.

CI/CD Pipelines

19. What causes a build to fail in OpenShift?

• Incorrect Git repository URL.
• Check with oc describe bc/my-build.
• Update BuildConfig with oc edit bc.
• Validate in test project.
• Monitor with Prometheus.
• Fix authentication issues.

Builds fail to complete, requiring configuration fixes.

20. Why does a pipeline timeout?

Pipelines timeout due to insufficient resources. Increase limits in BuildConfig YAML with oc edit bc/my-build. Validate in a test project and monitor with Prometheus to resolve timeouts.

21. When does a build fail to trigger?

• Missing webhook in Git repository.
• Configure with oc set triggers bc/my-build.
• Verify Git access with secrets.
• Validate in test project.
• Monitor with Prometheus.
• Ensure trigger automation.

Builds don’t start, requiring trigger configuration.

22. Where do you check pipeline errors?

Check pipeline errors with oc logs pipeline/my-pipeline and TaskRun events with oc describe taskrun. Validate in a test project to identify issues. Monitor with Prometheus to ensure pipeline stability.

23. Who resolves build authentication issues?

• DevOps engineers fix credentials.
• Add secrets with oc create secret.
• Collaborate with developers for access.
• Validate in test project.
• Monitor with Prometheus.
• Ensure repository access.

Builds fail authentication, requiring secure fixes.

24. Which tools debug pipeline failures?

Pipelines fail due to misconfigurations. Use oc logs pipeline/my-pipeline and oc describe pipeline for diagnostics.

• Validate in test project.
• Monitor with Prometheus.
• Check TaskRun configurations.
• Fix pipeline YAML.

Failures disrupt CI/CD, requiring debugging skills.

25. How do you fix a stuck pipeline?

• Check TaskRun status with oc describe taskrun.
• Restart pipeline with oc start-build.
• Verify resource limits in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Clear stuck pods.

Pipelines halt, requiring immediate resolution.

26. What prevents image pushes to the registry?

Image pushes fail due to registry authentication issues. Add credentials with oc create secret docker-registry. Validate in test project and monitor with Prometheus to resolve registry issues.

27. Why does a build consume excessive resources?

• High memory in BuildConfig YAML.
• Check with oc describe bc/my-build.
• Reduce limits in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Optimize build process.

Builds overload the cluster, requiring resource tuning.

28. When does a pipeline fail to deploy?

Pipelines fail deployment due to incorrect image tags. Update with oc tag my-image:latest in BuildConfig. Validate in a test project for successful deployment. Monitor with Prometheus to resolve deployment issues.

29. Where do you monitor build performance?

• Use Prometheus for build metrics.
• Check duration with oc describe bc/my-build.
• Visualize with Grafana dashboards.
• Validate in test project.
• Monitor with alerts.
• Optimize build resources.

Builds run slowly, requiring performance monitoring.

30. Who fixes pipeline configuration errors?

DevOps engineers correct pipeline YAML with oc edit pipeline/my-pipeline and collaborate with developers for requirements.

• Validate in test project.
• Monitor with Prometheus.
• Check TaskRun settings.
• Ensure pipeline stability.

Pipelines fail, requiring configuration fixes.

31. Which metrics indicate pipeline issues?

• Monitor build failure rates in Prometheus.
• Track TaskRun duration metrics.
• Analyze with scripts.
• Validate in test project.
• Monitor pipeline efficiency.
• Set failure alerts.

Pipelines fail frequently, requiring metric analysis.

32. How do you secure pipeline credentials?

Pipelines expose sensitive data. Store credentials in Secrets with oc create secret generic my-secret. Validate in a test project to ensure secure pipeline execution.

33. What causes build dependency failures?

• Missing libraries in builder image.
• Check logs with oc logs bc/my-build.
• Update Dockerfile or S2I config.
• Validate in test project.
• Monitor with Prometheus.
• Fix build scripts.

Builds fail compilation, requiring dependency fixes.

34. Why does a pipeline fail intermittently?

Intermittent failures occur due to resource contention. Check with oc describe bc/my-build and increase limits in YAML. Validate in a test project to stabilize pipelines. Monitor with Prometheus to resolve intermittent issues.

35. When does a build need custom images?

• Use custom images for complex builds.
• Define Dockerfile in repository.
• Configure BuildConfig with oc edit bc.
• Validate in test project.
• Monitor with Prometheus.
• Ensure build completion.

Standard images fail, requiring custom configurations.

Networking

36. What causes a Route to be inaccessible?

• Incorrect service selector in Route.
• Check with oc describe route/my-route.
• Update route YAML with oc edit route.
• Validate in test project.
• Monitor with Prometheus.
• Ensure service connectivity.

Users cannot access apps, requiring Route fixes.

37. Why does a pod fail to communicate?

• Network policy blocks traffic.
• Check with oc describe networkpolicy.
• Update policy YAML to allow traffic.
• Validate in test project.
• Monitor with Prometheus.
• Fix pod selectors.

Pods are isolated, requiring network policy adjustments.

38. When does a Route return 504 errors?

Routes timeout due to backend service issues. Check with oc describe route/my-route and verify pod health with oc describe pod. Validate in a test project to resolve errors.

39. Where do you debug network issues?

• Use oc describe pod for connectivity errors.
• Run oc exec for network tests.
• Check Route with oc describe route.
• Validate in test project.
• Monitor with Prometheus.
• Use tcpdump for diagnostics.

Network failures occur, requiring detailed debugging.

40. Who resolves Route access issues?

Admins fix Route configurations with oc edit route/my-route and ensure RBAC settings. Validate in a test project and monitor with Prometheus to resolve access issues.

41. Which tools diagnose network latency?

• Use Prometheus for traffic metrics.
• Run curl for response times.
• Integrate with Istio for observability.
• Validate in test project.
• Monitor with Grafana.
• Optimize network policies.

Apps experience delays, requiring latency diagnostics.

42. How do you fix Route TLS errors?

Routes fail secure connections. Update certificates with oc create route edge --cert my-cert.pem. Validate in a test project.

• Monitor with Prometheus.
• Ensure certificate validity.
• Check Route configuration.
• Update firewall rules.

TLS errors block access, requiring secure fixes.

43. What causes pod-to-pod communication failures?

• Strict network policies block traffic.
• Check with oc describe networkpolicy.
• Update selectors in policy YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure pod connectivity.

Pods cannot communicate, requiring policy adjustments.

44. Why does a service fail to route traffic?

Services fail due to incorrect pod selectors. Verify with oc describe svc/my-service and update selector in YAML. Validate in a test project to restore traffic routing.

45. When does a Route need re-encryption?

• Use re-encryption for secure backend.
• Configure with oc create route reencrypt.
• Validate certificate in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure secure routing.

Secure apps require re-encryption, fixing connectivity issues.

46. Where do you monitor network traffic?

Monitor traffic with Prometheus via Cluster Monitoring Operator. Analyze with Grafana dashboards. Validate in test project to resolve traffic issues.

47. Who fixes network policy errors?

• Admins update networkpolicy.yaml.
• Check with oc describe networkpolicy.
• Collaborate with developers for needs.
• Validate in test project.
• Monitor with Prometheus.
• Ensure policy accuracy.

Policies block traffic, requiring configuration fixes.

48. Which steps secure network access?

Unauthorized access occurs. Configure network policies with oc apply -f policy.yaml and restrict with RBAC.

• Validate in test project.
• Monitor with Prometheus.
• Ensure least privilege.
• Check audit logs.

Security breaches require network restrictions.

49. How do you optimize Route performance?

• Adjust timeout in route YAML.
• Monitor latency with Prometheus.
• Scale backend pods with oc scale.
• Validate in test project.
• Monitor with Grafana.
• Optimize service settings.

Routes are slow, requiring performance tuning.

50. What causes Route 503 errors?

Backend pods fail readiness checks, causing 503 errors. Check with oc describe pod/my-pod and update probes in YAML. Validate in a test project and monitor with Prometheus to resolve errors.

51. Why does OVN-Kubernetes block traffic?

• Misconfigured OVN-Kubernetes policies.
• Check with oc describe network.operator.
• Update network policy YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure pod connectivity.

Network blocks apps, requiring policy fixes.

52. When does a load balancer fail?

Load balancers fail due to misconfigured Routes. Update with oc edit route/my-route and verify backend health. Validate in a test project to restore traffic. Monitor with Prometheus to resolve balancing issues.

Storage

53. What causes a PVC to fail binding?

• No matching Persistent Volume.
• Check with oc describe pvc/my-pvc.
• Update storage class in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure PV availability.

Pods cannot mount storage, requiring binding fixes.

54. Why does a pod fail to mount storage?

Pods fail to mount due to incorrect PVC configuration. Verify with oc describe pvc/my-pvc and ensure storage class compatibility. Validate in a test project to resolve mount issues.

55. When does a PVC need resizing?

• Storage runs low for apps.
• Expand with oc edit pvc/my-pvc.
• Verify storage class support.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data availability.

Apps run out of space, requiring resizing.

56. Where do you debug storage errors?

Debug storage errors with oc describe pvc/my-pvc and pod events with oc describe pod/my-pod. Validate in test project to resolve storage issues.

57. Who resolves storage provisioning issues?

• Admins configure storage classes.
• Check with oc describe storageclass.
• Collaborate with developers for needs.
• Validate in test project.
• Monitor with Prometheus.
• Fix PVC bindings.

Storage fails to provision, requiring admin fixes.

58. Which tools diagnose storage performance?

Storage performance is slow. Use Prometheus for IOPS metrics and oc describe pvc/my-pvc for errors. Validate in a test project to optimize performance.

59. How do you fix PV reclaim issues?

• Incorrect reclaim policy in PV.
• Check with oc describe pv/my-pv.
• Update policy to Delete/Retain.
• Validate in test project.
• Monitor with Prometheus.
• Ensure PV reuse.

PVs cannot be reclaimed, requiring policy fixes.

60. What causes storage access errors?

Pods cannot access storage due to RBAC or SCC restrictions. Check with oc describe pod/my-pod and update permissions with oc adm policy add-scc-to-user.

• Validate in test project.
• Monitor with Prometheus.
• Ensure secure access.
• Fix SCC settings.

Access errors block apps, requiring permission fixes.

61. Why does a volume snapshot fail?

• Misconfigured CSI driver.
• Check with oc describe volumesnapshot.
• Update snapshot YAML configuration.
• Validate in test project.
• Monitor with Prometheus.
• Ensure snapshot creation.

Backups fail, requiring snapshot configuration fixes.

62. When does a pod lose persistent data?

Data is lost after pod restart due to missing PVC. Configure PVC in DeploymentConfig YAML with oc edit dc/my-app. Validate in a test project to ensure persistence.

63. Where do you store volume snapshots?

• Store in CSI-compatible backend.
• Configure with oc apply -f snapshot.yaml.
• Ensure secure storage access.
• Validate in test project.
• Monitor with Prometheus.
• Verify snapshot integrity.

Snapshots are unavailable, requiring storage fixes.

64. Who fixes storage class misconfigurations?

Admins correct storage class YAML with oc edit storageclass and ensure CSI driver compatibility. Validate in a test project to resolve provisioning issues. Monitor with Prometheus to ensure stability.

65. Which steps restore lost data?

• Restore from volume snapshot.
• Apply with oc apply -f restore.yaml.
• Verify PVC binding with oc describe pvc.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data integrity.

Data loss occurs, requiring restoration steps.

66. How do you automate storage provisioning?

Storage provisioning fails manually. Use storage classes with AWS EBS for dynamic provisioning.

• Apply with oc apply -f storageclass.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure scalability.

Automation resolves provisioning issues.

67. What causes slow storage performance?

• 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.

Apps experience storage delays, requiring performance tuning.

68. Why does a StatefulSet lose data?

Data loss occurs due to incorrect PVC bindings. Verify with oc describe statefulset/my-app and update YAML. Validate in a test project to ensure data persistence.

69. When does a storage class fail provisioning?

• Misconfigured CSI driver settings.
• Check with oc describe storageclass.
• Update storage class YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure provisioning success.

PVCs fail to provision, requiring configuration fixes.

Monitoring

70. What causes missing Prometheus metrics?

Metrics are unavailable due to incorrect ServiceMonitor annotations. Update with oc edit servicemonitor/my-monitor and verify pod annotations. Validate in a test project to restore metrics. Monitor with Grafana to ensure observability.

71. Why do alerts trigger falsely?

• Incorrect thresholds in PrometheusRule.
• Check with oc describe prometheusrule.
• Update alert conditions in YAML.
• Validate in test project.
• Monitor with Grafana.
• Optimize alert rules.

False alerts disrupt operations, requiring rule adjustments.

72. When does monitoring fail to detect issues?

• Missing ServiceMonitor for app.
• Configure with oc apply -f servicemonitor.yaml.
• Verify pod annotations.
• Validate in test project.
• Monitor with Prometheus.
• Ensure metric collection.

Issues go undetected, requiring monitoring configuration.

73. Where do you check app logs?

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

Logs are missing, requiring log collection fixes.

74. Who resolves monitoring failures?

• Admins debug Prometheus pods.
• Check with oc describe pod/prometheus.
• Update Cluster Monitoring Operator.
• Validate in test project.
• Monitor with Grafana.
• Ensure observability.

Monitoring fails, requiring admin intervention.

75. Which tools fix log collection issues?

• Use EFK stack for logging.
• Configure Fluentd with oc edit clusterlogging.
• Visualize logs in Kibana.
• Validate in test project.
• Monitor with Prometheus.
• Fix log forwarding.

Logs are unavailable, requiring logging tool fixes.

76. How do you fix high monitoring latency?

Monitoring is slow due to overloaded Prometheus pods. Scale pods with oc scale statefulset/prometheus and optimize retention policies.

• Validate in test project.
• Monitor with Grafana.
• Reduce metric overhead.
• Ensure performance stability.

Latency impacts monitoring, requiring optimization.

77. What causes missing app logs?

• Misconfigured Fluentd in EFK stack.
• Check with oc describe clusterlogging.
• Update log forwarding settings.
• Validate in test project.
• Monitor with Prometheus.
• Ensure log collection.

Logs are unavailable, requiring EFK configuration fixes.

78. Why do alerts fail to notify?

• Incorrect Alertmanager configuration.
• Check with oc describe alertmanager.
• Update notification settings in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Integrate with PagerDuty.

Alerts don’t reach teams, requiring notification fixes.

79. When does Prometheus fail to scrape metrics?

• Incorrect pod annotations for scraping.
• Update ServiceMonitor with oc edit servicemonitor.
• Verify network connectivity.
• Validate in test project.
• Monitor with Grafana.
• Ensure metric collection.

Metrics are missing, requiring scraping configuration.

80. Where do you analyze performance issues?

• Use Prometheus for app metrics.
• Visualize with Grafana dashboards.
• Check resource usage with oc adm top pod.
• Validate in test project.
• Monitor with alerts.
• Optimize app performance.

Apps are slow, requiring performance analysis.

81. Who fixes alert configuration errors?

• Admins update PrometheusRule YAML.
• Check with oc describe prometheusrule.
• Collaborate with developers for metrics.
• Validate in test project.
• Monitor with Grafana.
• Ensure alert accuracy.

Alerts misfire, requiring configuration fixes.

82. Which steps optimize monitoring performance?

• Scale Prometheus pods with oc scale.
• Optimize retention policies in YAML.
• Reduce metric collection overhead.
• Validate in test project.
• Monitor with Grafana.
• Ensure monitoring efficiency.

Monitoring is slow, requiring performance tuning.

83. How do you fix log forwarding issues?

Logs are not forwarded due to Fluentd misconfiguration. Update with oc edit clusterlogging and verify Elasticsearch connectivity. Validate in a test project to restore logging.

84. What causes high CPU usage alerts?

• App consumes excessive CPU.
• Check with oc adm top pod.
• Adjust resource limits in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Optimize app code.

Alerts trigger for CPU, requiring resource fixes.

85. Why does EFK logging fail?

• Elasticsearch pod crashes.
• Check with oc describe pod/elasticsearch.
• Update clusterlogging YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure log collection.

Logs are unavailable, requiring EFK fixes.

Cluster Management

86. What causes a node to become NotReady?

• Resource exhaustion or network issues.
• Check with oc describe node.
• Drain with oc adm drain node-name.
• Validate in test project.
• Monitor with Prometheus.
• Replace via MachineSets.

Nodes fail, requiring diagnostics and recovery.

87. Why does etcd performance degrade?

• High disk latency or compaction issues.
• Check with oc adm inspect etcd.
• Optimize etcd configuration.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure etcd stability.

Cluster slows down, requiring etcd tuning.

88. When does a cluster upgrade fail?

Upgrades fail due to operator incompatibilities. Check with oc get clusteroperators and resolve conflicts in YAML. Validate in a test cluster to complete the upgrade. Monitor with Prometheus to ensure stability.

89. Where do you check cluster health?

• Use oc get clusteroperators for status.
• Monitor metrics in Prometheus.
• Check logs in OpenShift Web Console.
• Validate in test cluster.
• Monitor with Grafana.
• Ensure cluster stability.

Cluster issues occur, requiring health checks.

90. Who resolves node failures?

• Admins debug with oc describe node.
• Collaborate with developers for pod issues.
• Drain with oc adm drain node-name.
• Validate in test cluster.
• Monitor with Prometheus.
• Replace failed nodes.

Nodes crash, requiring admin intervention.

91. Which tools automate cluster maintenance?

• Use Ansible for node patching.
• Configure MachineSets for scaling.
• Integrate with Prometheus alerts.
• Validate in test cluster.
• Monitor with Grafana.
• Ensure minimal disruption.

Maintenance is manual, requiring automation.

92. How do you recover a failed node?

Nodes fail due to hardware issues. Drain with oc adm drain node-name, replace via MachineSets, and validate in a test cluster to restore functionality.

93. What causes etcd data corruption?

• Disk failures or network partitions.
• Check with oc adm inspect etcd.
• Restore from backup with oc adm restore.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure etcd integrity.

Cluster fails, requiring etcd recovery.

94. Why does a cluster operator fail?

• Incompatible operator versions.
• Check with oc get clusteroperators.
• Update via OperatorHub.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure operator stability.

Operators crash, requiring version fixes.

95. When does a node need draining?

Drain nodes during maintenance or failures using oc adm drain node-name. Validate in a test cluster to minimize disruption. Monitor with Prometheus to ensure successful draining.

96. Where do you store etcd backups?

• Store in secure external storage.
• Back up with oc adm backup etcd.
• Ensure access via RBAC.
• Validate in test cluster.
• Monitor with Prometheus.
• Verify backup integrity.

Backups are inaccessible, requiring secure storage.

97. Who fixes cluster upgrade issues?

• Senior admins run oc adm upgrade.
• Check logs with oc get clusteroperators.
• Collaborate with developers for compatibility.
• Validate in test cluster.
• Monitor with Prometheus.
• Resolve operator conflicts.

Upgrades fail, requiring admin expertise.

98. Which steps minimize cluster downtime?

• Use rolling upgrades for operators.
• Pre-test in a staging cluster.
• Monitor with oc get clusteroperators.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure minimal disruption.

Upgrades cause outages, requiring careful planning.

99. How do you fix pod scheduling issues?

• Insufficient node resources.
• Check with oc describe node.
• Add taints or node selectors.
• Validate in test cluster.
• Monitor with Prometheus.
• Scale nodes if needed.

Pods fail to schedule, requiring resource adjustments.

100. What causes cluster resource exhaustion?

• Overloaded pods on nodes.
• Check with oc adm top nodes.
• Scale nodes with MachineSets.
• Validate in test cluster.
• Monitor with Prometheus.
• Optimize resource limits.

Cluster slows down, requiring resource management.

101. Why do pods fail to schedule?

• Taints or affinity rules block scheduling.
• Check with oc describe node.
• Update pod YAML with tolerations.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure scheduling success.

Pods remain unscheduled, requiring configuration fixes.

102. When does a cluster need scaling?

Scale clusters during high workloads using MachineSets or oc adm manage-node. Validate in a test cluster to ensure capacity. Monitor with Prometheus to maintain performance.

103. Where do you monitor upgrade progress?

• Use oc get clusteroperators for status.
• Check logs in OpenShift Web Console.
• Monitor with Prometheus dashboards.
• Validate in test cluster.
• Ensure upgrade completion.
• Track operator status.

Upgrades stall, requiring progress monitoring.